Skip to main content
Glama

Social0

suggest_best_platforms

Read-onlyIdempotent

Analyze post content and recommend which social platforms are the best fit. Considers text length, media presence, and connected accounts. Example: 'Which platforms should I publish this to?'

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": {
      "content": "<content>"
    },
    "name": "suggest_best_platforms"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesPost content to analyze
has_mediaNo
media_typeNoExplicit content type. Prefer image/video/collection over only toggling has_media.
media_is_videoNoWhether attached media is video

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description usefully adds that results depend on connected accounts (explaining the open-world dependency), but says nothing about the output format or how recommendations are ranked.

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?

Two short sentences plus a clarifying example question, front-loaded with the core action. No filler, though the example is somewhat redundant with the first sentence.

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 read-only advisory tool with no output schema, it should say what is returned (e.g. a ranked list of platform names). The factors considered are listed, but the response shape an agent must interpret is left unstated.

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 description coverage is 75%, so the baseline is 3. The description's mention of text length, media presence and connected accounts loosely maps to content, has_media and media_type, but it does not clarify the ambiguous overlap between media_type and media_is_video.

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?

States a specific verb and resource: 'Analyze post content and recommend which social platforms are the best fit.' This clearly separates it from publishing siblings like publish_post or schedule_post, though it never names a sibling explicitly.

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?

The example question ('Which platforms should I publish this to?') implies the usage context, and 'connected accounts' hints at prerequisites. However, there is no explicit when-to-use vs when-not guidance or naming of alternatives such as list_accounts for raw account data.

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.