Skip to main content
Glama

Social0

list_posts

Read-onlyIdempotent

List the user's Social0 posts with optional filters by status, platform, account, or search text. Use when the user asks to see drafts, scheduled posts, or published content. Example: 'Show all scheduled posts.'

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
limitNo
searchNoSearch in post content
statusNoFilter by post status
accountNoFilter by connected account UUID or unambiguous platform name
platformNoFilter by platform
connected_account_idNoFilter by connected account UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 adds only the filterable dimensions and reveals nothing about result ordering, default page size, or what happens when no posts match. That is adequate but thin for a read tool with no output schema.

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?

Three short sentences, front-loaded with purpose, then guidance, then an example. The example slightly restates the preceding sentence ('scheduled posts') but it is short and aids query matching; nothing else is wasted.

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 six-optional-parameter list tool with full annotation coverage and no output schema, the description is nearly sufficient, but it omits default page size and result ordering, which an agent needs to decide whether to set limit or paginate. The account versus connected_account_id overlap is also left unresolved.

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 83%, so the schema already documents limit, search, status, account, platform and connected_account_id with enums. The description restates the filter categories at a high level but does not clarify the ambiguity between 'account' (which accepts a UUID or a platform name) and 'connected_account_id', nor the default limit of 20. 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 the user's Social0 posts') plus the available filter dimensions, which separates it from single-post siblings like get_post. It stops short of naming a sibling explicitly, so the differentiation is implied by the plural 'List' rather than stated.

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 a clear trigger ('Use when the user asks to see drafts, scheduled posts, or published content') and reinforces it with a concrete example utterance. No exclusions or alternatives are given, which is acceptable here since the listing role is unambiguous, but 'when not to use' is absent.

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.