Convocore

create_channel_connect_link

Create a private link the USER opens to connect WhatsApp, Messenger or Instagram to an agent. Connecting needs the user to log in with Meta in their own browser, so you cannot do it for them: create the link, show the returned url to the user as a clickable link, and tell them to come back and say when they are done. The page needs no Convocore login and expires (default 30 minutes). When the user says they finished, call get_agent_channels to confirm the channel is really connected before saying it works. messenger and instagram use the same page: the user picks a Facebook page; Instagram is connected when an Instagram account is linked to that page. whatsappConnectionMode: metaCloudApi (default, a number used only by the AI) or metaCoexistence (a number already used in the WhatsApp Business app, shared with the AI).

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": {
      "channel": "<channel>",
      "agentId": "<agentId>"
    },
    "name": "create_channel_connect_link"
  }
}

Input Schema

Name	Required	Description
`agentId`	Yes
`channel`	Yes
`ttlMinutes`	No	How long the link works. Default 30, max 1440.
`whatsappConnectionMode`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare non-read-only, non-destructive, non-idempotent; the description adds materially more — the link is private, needs no Convocore login, expires by default after 30 minutes, and the channel is not actually connected until verified. That is the kind of context the annotations cannot express.

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

Conciseness4/5

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

Front-loaded with the action and the user-in-the-loop constraint, and every sentence carries operational information. It is a dense single block, though, and the channel-mode detail could be separated for easier scanning.

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

Completeness5/5

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

There is no output schema, and the description covers the return value ('the returned url'), the expiry behavior, the required post-step verification, and the per-channel nuances. An agent has everything needed to call it and act on the result.

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

Parameters4/5

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

Schema coverage is only 25%, but the description compensates by explaining whatsappConnectionMode in depth (metaCloudApi = AI-only number vs metaCoexistence = number shared with the WhatsApp Business app) and by clarifying that messenger and instagram use the same page with Instagram connected via a linked account. agentId is left implicit, which keeps it below a 5.

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?

States a specific verb and resource — create a private connect link — and pins down that it covers WhatsApp, Messenger and Instagram for an agent. This clearly separates it from read/verify siblings like get_agent_channels and get_connect_link_status.

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?

Gives the full usage contract: the user must log in with Meta in their own browser so the agent cannot do it for them, the returned url must be shown as a clickable link, and the user must be told to come back. It also names get_agent_channels as the verification step, which is explicit routing to an alternative tool for a different job.

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

All Convocore tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?