Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

list_posts

Retrieve drafts, scheduled, and published posts with IDs, status, type, preview, schedule time, and target accounts to find a post to edit, publish, or check.

Instructions

List your posts (drafts, scheduled, and published) with their IDs — use this to find a post to edit, publish, or check. Returns each post's ID, status, type, a text preview, schedule time, and target accounts.

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_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20)
statusNoFilter by status. Use "scheduled" for posts queued to publish at a future time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden, and it does so reasonably: it names every field returned (ID, status, type, text preview, schedule time, target accounts) so the agent knows the payload shape, and 'List' signals a non-mutating read. It omits pagination behavior and any permission requirements, which leaves residual gaps for an annotation-free tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action, then the return payload. No filler, no repetition of the tool name, and the purpose clause lands before the detail.

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 simple two-optional-parameter read tool with no annotations or output schema, the description supplies both usage context and the return field list, which is the main missing structured information. Minor residual gaps are pagination and auth requirements, but nothing prevents a correct invocation.

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 limit (max 50, default 20) and the status enum including what 'scheduled' means. The description adds no filtering or format detail beyond the structured fields, so the baseline 3 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?

The description gives a specific verb and resource ('List your posts') and enumerates the statuses covered (drafts, scheduled, published) plus the returned identifiers. It is clear about what the tool does, though the phrase 'or check' brushes against the sibling check_post_status without distinguishing itself from it.

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?

It states concrete downstream uses — find a post to edit, publish, or check — which tells an agent the context in which to reach for this tool. It stops short of naming an alternative or an exclusion case, so the routing is implied rather than explicit.

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