Skip to main content
Glama

List recent posts

list_posts
Read-only

Read the user's recent posts and drafts with per-network status, the live link once a post is up, and the reason when one failed. Published posts include engagement metrics (likes, comments, shares, engagementRate - impressions on plans with full analytics) once analytics have synced. Use it to avoid duplicating a topic AND to learn which topics performed before drafting the next post.

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 15)
statusNoFilter by status (posted and published are synonyms)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description then adds value by disclosing return contents and data-availability conditions (metrics appear once analytics sync, impressions only on plans with full analytics). It does not mention pagination or result-ordering behavior beyond 'recent', which keeps it from a 5.

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?

Front-loaded with the resource and the returned fields, then the usage rationale. Two sentences carry a lot of information with little waste, though the metric-caveat clause makes the second sentence dense.

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 no output schema, the description must explain returns and it largely does: status, link, failure reason, and conditional engagement metrics. Pagination and ordering semantics are the only gaps, and default limit is covered by the schema, so it is close to complete for a simple read tool.

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% and both parameters (limit, status enum with synonym note) are fully documented in the schema, so baseline 3 applies. The description adds no syntax, defaults, or filtering detail beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (read/list) and resource (recent posts and drafts) with the exact scope of returned data: per-network status, live link, failure reason, engagement metrics. None of the siblings (create_draft, get_growth, list_accounts, shape_post, get_upload_url) overlap this resource, so an agent can route here without ambiguity.

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?

Explicit when-to-use is given: avoid duplicating a topic and learn which topics performed before drafting the next post. That ties the tool to a concrete workflow decision. It stops short of naming an alternative tool or stating when not to use it, so it is clear context but not full exclusion guidance.

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.

Resources