Skip to main content
Glama
Content Drifter MCP

Content Drifter MCP

Official
by OPTRIXTECH

list_platform_connections

Lists connected social platforms and reports each connection’s health, including Pinterest board access and Bluesky reconnect status.

Instructions

List connected social platforms and connection health (e.g. Pinterest boards, Bluesky reconnect).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_platform_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does little with it. It never states that this is a read-only operation, whether results are paginated, whether it requires authentication, or what 'reconnect' status actually implies for the caller. The only behavioral hint is the notion of 'connection health', which is left undefined.

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?

A single front-loaded sentence with the resource stated first and the illustrative parenthetical second — no wasted wording. The examples are slightly terse ('Bluesky reconnect') but they add concreteness rather than noise.

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

Completeness3/5

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

For a simple zero-parameter read tool with no output schema, the description is adequate but thin: it names the resource and gestures at health status without saying what the response contains (per-platform entries? a status enum?). With no annotations to cover the read-only and auth profile, the definition should do more.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; schema coverage is 100% and the empty object schema matches the description's parameterless framing. Baseline 4 applies for a no-parameter tool.

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?

Specific verb + resource: "List connected social platforms and connection health." The parenthetical examples (Pinterest boards, Bluesky reconnect) concretize what 'connection health' means, and the resource is plainly distinct from siblings like list_upcoming_posts or schedule_post. It stops short of explicitly contrasting with any sibling, so 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied — an agent can reasonably infer this is the discovery/diagnostic call to make before publishing or scheduling. There is no explicit statement of when to call it, when not to, or which sibling to use instead if the goal is to fix a broken connection.

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