Skip to main content
Glama

List publications

list_publications
Read-only

List publications in a profile, newest first. With status scheduled they are listed soonest first: use it to see what is scheduled. status draft lists saved drafts. Filter by platform or accountId; page with cursor.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPublications per page, 1–100. Defaults to 25.
cursorNonextCursor from the previous page.
statusNoOnly publications in this status. Scheduled ones are listed soonest first; others newest first.
platformNoOnly publications with a target on this platform.
accountIdNoOnly publications with a target on this account.
profileIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavior: default newest-first ordering except scheduled status, which reverses to soonest-first, plus cursor paging. It says nothing about the shape or volume of returned publications, which matters since there is 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.

Conciseness5/5

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

Four short sentences, front-loaded with the core action and ordering, then filtering and paging. Every clause carries signal and there is 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?

For a read-only, six-parameter list tool with no output schema, the description covers ordering, the two filter axes, and pagination well. The gaps are minor: profileId is only implied by 'in a profile', and nothing hints at what a publication record contains.

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 explains limit, cursor, status, platform, accountId, and their enums. The description reiterates status-specific ordering and cursor paging but adds no new parameter meaning, and never mentions profileId or limit defaults. Baseline 3 applies when the schema does the heavy lifting.

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 pairs the specific verb 'List' with the resource 'publications' and adds scope ('in a profile') and default ordering ('newest first'). It does not name a sibling, so differentiation from tools like list_posts is left to inference, but the purpose is unambiguous.

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 gives concrete when-to-use context: status=scheduled is for 'see what is scheduled' and status=draft for 'saved drafts'. It stops short of exclusions or naming an alternative tool for adjacent needs, so it is clear but not fully routing.

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