Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

check_post_status

Check the publishing status of a post using its ID to confirm whether it was published, queued, or failed.

Instructions

Check the publishing status of a post by its ID.

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": {
      "postId": "<postId>"
    },
    "name": "check_post_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post ID returned from post_text or schedule_post

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/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 almost nothing with it. It never says whether this is a safe read-only call, what status values can come back (queued/published/failed), whether polling is expected, or whether the check has side effects or rate limits.

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 no filler or redundancy. It earns its brevity, though the terseness leaves the ambiguity noted in other dimensions unaddressed.

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?

The tool is simple (one required string parameter) and has no output schema, so the description should at least sketch what a 'status' looks like. It doesn't, leaving the agent to guess the return values for a status-polling call.

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 coverage is 100% and the schema already explains the parameter as 'the post ID returned from post_text or schedule_post'. The description's 'by its ID' adds no meaning beyond that, so the baseline 3 for fully documented parameters applies.

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 ('Check the publishing status of a post') plus the lookup key ('by its ID'), which separates it from neighbors like get_post_analytics or list_posts. It does not explicitly name any sibling as the alternative, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of when not to use it, and no pointer to alternatives such as list_posts or get_post_analytics. The only contextual clue ('post ID returned from post_text or schedule_post') lives in the schema, not the description.

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