unlink_resource
Clear the connector place from a resource, reverting it to an unlinked placeholder the creator can relink through the connector.
Clear the connector place (space) from a resource, reverting it to an unlinked placeholder row the creator can relink through the connector with request_resource_link. Delegates to an Action so a project.resource.unlinked event fires. No-op if the resource is already unlinked.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Fires one event
Delivered to every endpoint subscribed to it once the change is made.
Annotations
A client that honours annotations asks a person before running it. Sending the same arguments twice changes nothing the second time. It reaches beyond Subscriby: a connector, a provider or a member.
Arguments
resource_id*stringUUID of the resource to unlink.
What it returns
{ "data": { "id": "b73c5f21-9d80-4a6e-8215-4f70ce13a9d6", "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "kind": "telegram:channel", "connector": "telegram", "space": null, "title": "Research Channel", "description": null, "active": true, "created_at": "2026-05-18T10:05:00Z", "updated_at": "2026-09-06T08:30:12Z" }}The full get_resource row with space cleared. The resource keeps its kind and connector: it is still a Telegram channel resource, only one bound to no place until the creator links another.
How it fails
RESOURCE_NOT_FOUNDunknown resource_id, or the parent project is outside the token's scope.
TOKEN_MISSING_ABILITYtoken lacks project-resource:update.
How is this guide?
Last updated on