Skip to main content
Glama

Check a platform connection

autoshort_get_connection_status
Idempotent

Checks if a social platform account is connected and returns the linked account or a short, single-use consent link the user must open to authorize access.

Instructions

Is this platform connected? If yes, returns the account. If not, returns connectUrl: a short, single-use link (expires in 15 minutes) that opens the platform's consent screen directly. Give it to the user — that consent is the only human step, once per platform — then call this again every 10 seconds (pollAfterSeconds) until connected is true and continue on your own. Polling reuses the same unexpired link. YouTube, Facebook, Instagram and Threads need a paid plan; Facebook/Instagram/Threads answer PLATFORM_PENDING_APPROVAL where Meta has not enabled them for the account yet. Free.

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": {
      "platform": "<platform>"
    },
    "name": "autoshort_get_connection_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.6/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: link lifetime (15 minutes), single-use semantics, that consent is the only human step and happens once per platform, that polling is safe and reuses the link, and the PLATFORM_PENDING_APPROVAL response state. The annotations set readOnlyHint=false, which the description implicitly justifies since the call can mint a connect link; it does not contradict them. A small gap remains in not stating the exact error/response shape for other failure modes.

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 core question and branching answer, then instructions, then plan caveats in priority order. Every clause carries information, but the single dense paragraph with nested parentheses makes it slightly harder to scan than a cleanly segmented version.

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?

No output schema exists, so the description carries the return-value burden and does so: it explains both the success payload (the connected account) and the failure payload (connectUrl with expiry), plus the special pending-approval state. For a one-parameter, no-output-schema tool, nothing an agent needs in order to call it correctly is missing.

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 0%, but with a single enum-typed platform parameter the description compensates by attaching meaning to specific values: which platforms require a paid plan and which can return PLATFORM_PENDING_APPROVAL. It never explicitly defines the parameter itself, which is why this lands at 4 rather than 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?

Opens with a direct question that names the exact operation (checking whether a platform is connected) and states both outcomes: the connected account, or a connectUrl. An agent can immediately tell this is a connection-state check plus consent-link generator, distinct from listing accounts or fetching capabilities.

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?

Explicitly routes the agent: hand the link to the user, call again every 10 seconds (pollAfterSeconds), continue until connected is true, and note that polling reuses the same unexpired link rather than minting new ones. It also specifies prerequisites per platform (paid plan for YouTube/Facebook/Instagram/Threads) and names the PLATFORM_PENDING_APPROVAL condition.

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