Convocore

meta_pages_read

Read-onlyIdempotent

Diagnose a connected Facebook page (Messenger / Instagram). To list connected pages use get_agent_channels; to connect one use create_channel_connect_link. Actions: check_subscriptions — which webhook events the page is subscribed to — use when the agent does not receive Messenger / Instagram messages Needs: pageId. | get_profile — name and picture of a Messenger / Instagram user who messaged the agent Needs: userId.

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": {
      "action": "<action>",
      "agentId": "<agentId>"
    },
    "name": "meta_pages_read"
  }
}

Input Schema

Name	Required	Description
`mode`	No	compact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
`action`	Yes
`origin`	No	For get_profile.
`pageId`	No	Facebook page id from get_agent_channels.
`userId`	No	For get_profile: the Messenger / Instagram user id (conversation id).
`agentId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds real value beyond that by disclosing what each action returns (webhook event subscriptions; name and picture of the messaging user) and flagging the diagnostic trigger condition. No auth or rate-limit context, but nothing is contradicted.

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-loads the purpose, then alternatives, then per-action detail, with no filler sentences. The pipe-delimited action blocks and the run-on "Needs:" clauses are dense but readable; minor tidying would earn a 5.

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 six-parameter, two-action read tool with no output schema, it covers both actions, their required inputs, and the routing to sibling tools. The undocumented agentId and the relationship between mode and returned data are the only meaningful omissions, and mode is fully specified in the schema.

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?

At 67% schema coverage the description usefully maps required inputs to actions — pageId for check_subscriptions, userId for get_profile — which the schema only partially signals. mode, origin and their enums are documented in the schema itself, and agentId is left undocumented in both places.

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

Purpose4/5

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

Opens with a specific verb-plus-resource ("Diagnose a connected Facebook page") and then enumerates the two concrete actions, check_subscriptions and get_profile, with what each returns. It also names the sibling tools it is not (get_agent_channels for listing, create_channel_connect_link for connecting), so an agent can place it correctly. "Diagnose" alone is slightly fuzzy for what is essentially two read endpoints.

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

Usage Guidelines4/5

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

Explicitly routes the agent: list pages with get_agent_channels, connect with create_channel_connect_link, and use check_subscriptions specifically "when the agent does not receive Messenger / Instagram messages." The only gap is that get_profile has no stated when-to-use beyond its data description.

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?