Skip to main content
Glama

list_posts_with_metrics

Read-only

List EVERY published post in a date range, newest first, a page at a time, with all its numbers. Use it for a full history or export ("all my posts this year with their stats"); for the best or worst few, use list_top_posts; to find one by its words, search_posts. Ranges may be longer than a year. Each post shows what its platform reports, as of the latest sync, so recent posts are still growing and platforms differ (LinkedIn adds members reached, saves, sends and more; a company page has fewer). When the reply ends with a cursor, call again with the same arguments plus that cursor for the next page; the last page has none. An empty range says "No posts found". Each row's post_id works with get_post_analytics and tag_published_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_with_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPosts per page (default 50, max 100).
authorNoWhose posts. "me" for the person asking, or a teammate's name. Omit for the whole workspace.
cursorNoThe cursor the previous page ended with. Omit for the first page.
periodNoRolling window ending today. Default 30d. For any other window, pass start_date/end_date instead.
end_dateNoOptional. Last day of a custom range, YYYY-MM-DD, inclusive. Defaults to today. Needs start_date.
platformNoOptional. Omit for every platform.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
start_dateNoOptional. First day of the range, YYYY-MM-DD, in the user's timezone. Overrides `period`. Any length of range is allowed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive, and the description adds substantial context beyond them: newest-first ordering, as-of-latest-sync metrics, that recent posts are still growing, that platforms report different metric sets (LinkedIn members reached/saves/sends; company pages fewer), and the empty-range message. It stops short of saying whether pagination is stable across new posts arriving mid-export, which is the one behavior an exporter would want.

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?

Front-loaded with the scope and payload, then routing alternatives, then range caveat, then pagination, then failure mode, then follow-up ids. Every sentence maps to a decision the caller has to make; no filler or restatement of the name.

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 an 8-parameter list tool with no output schema, it covers return shape (per-platform metrics as of latest sync), pagination, and the empty case, which is more than most. The remaining gap is the exact row fields and metric naming per platform, which an exporter would need to parse results reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still earns a bump by spelling out the cursor loop ("call again with the same arguments plus that cursor", last page has none) and by noting ranges may exceed a year, which reassures against the period enum's 7d/30d/90d framing. It adds little on author, platform, or workspace beyond what the schema already says.

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 and resource ("List EVERY published post") plus ordering (newest first), pagination (a page at a time), and payload (with all its numbers). It also names the two sibling tools it is not (list_top_posts, search_posts), so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ("full history or export, all my posts this year with their stats") and explicit when-not with named alternatives: list_top_posts for best/worst few, search_posts for lookup by words. It also gives the correct next step after a result via get_post_analytics and tag_published_post.

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