Skip to main content
Glama

disconnect_meta_page

Destructive

Disconnect a Facebook page from an agent: the agent stops answering Messenger and Instagram for that page. pageId comes from get_agent_channels. Confirm with the user first. To connect a page use create_channel_connect_link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agentId": "<agentId>",
      "pageId": "<pageId>"
    },
    "name": "disconnect_meta_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYes
agentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds the concrete effect (agent stops answering Messenger and Instagram) plus a confirmation requirement, which is genuine value beyond structured fields. It stops short of saying whether conversation history or channel data is retained, which matters for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the effect, then the parameter source, then the safety instruction and alternative. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-param destructive mutation with no output schema and no annotations explaining irreversibility, the description covers effect, source of pageId, and confirmation. The remaining gap is the fate of existing conversations and whether agentId/pageId must be an existing pairing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate; it does for pageId by naming get_agent_channels as the source. agentId is left entirely unexplained (no hint that it identifies which agent to detach the page from), so half the parameters remain undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb + resource + consequence: 'Disconnect a Facebook page from an agent: the agent stops answering Messenger and Instagram for that page.' It also explicitly distinguishes itself from the connect-path sibling create_channel_connect_link.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the precondition source for pageId (get_agent_channels) and an operational instruction ('Confirm with the user first'), plus names the inverse tool. That is explicit when-to-use and when-to-use-the-other guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources