Social Post Flow

List Posts Tool

list-posts-tool

Read-only

List the user's social media posts. Supports filtering by profile and status, with pagination.

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

Input Schema

Name	Required	Description
`page`	No	Page number for pagination.
`order`	No	Sort direction: asc or desc.
`status`	No	Filter by status: scheduled, posted, failed.
`order_by`	No	Field to order by: scheduled_at, posted_at, created_at.
`per_page`	No	Number of results per page (default 10, max 100).
`social_profile_id`	No	Filter posts to a specific profile ID.

Output Schema

Name	Required	Description	Default
`data`	No
`meta`	No
`links`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear without the description. The description adds filtering and pagination context, but it does not disclose other behavioral details such as result ordering defaults 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.

Conciseness5/5

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

The description is a single tight sentence that front-loads the core action and then summarizes supported capabilities. Every clause contributes useful information with no filler.

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?

With full schema coverage, rich annotations, and an output schema, the description is sufficient for an agent to understand the tool's purpose and basic capabilities. Minor gaps around sorting and defaults are covered by the schema and do not seriously impair 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 description coverage is 100%, so all six parameters are already well documented in the input schema. The description mentions profile filtering, status filtering, and pagination, but adds no syntax or constraints beyond what the schema already provides.

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 clearly states a specific verb and resource: listing the user's social media posts. It implies a collection-returning operation distinct from get-post-tool, but it does not explicitly name or differentiate from sibling tools.

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 description indicates that filtering by profile and status is supported and that pagination is available, which implies intended usage. However, it gives no explicit when-to-use guidance, prerequisites, or comparison to alternatives such as get-post-tool or list-profiles-tool.

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

All Social Post Flow tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?