Skip to main content
Glama

List post drafts

flypost_list_drafts
Read-only

List the project's LinkedIn post drafts with status and publish state. publish_status filters by where a post is on LinkedIn: ['scheduled','publishing'] is the calendar (soonest first), ['published'] what went out, ['failed'] what needs a retry.

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": "flypost_list_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNoWriting status of the draft.
project_idNoProject id; omit for the active project.
publish_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false, closed-world). The description adds genuinely new behavior: scheduled/publishing results are ordered soonest-first and represent the calendar, which an agent cannot infer from the schema. It stops short of covering default limit, pagination, or overall ordering for other filters.

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?

Two tight sentences, zero filler. The core purpose is front-loaded and the filter semantics follow immediately, with no repetition of the title or schema.

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 simple read-only list tool with no output schema and no required params, the description covers purpose and the most nuanced filter. Minor gaps remain around the undocumented limit parameter and the shape of returned items, which the description only hints at via 'with status and publish state'.

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 50%: status and project_id are documented in the schema, while limit has no description anywhere. The description compensates partially for publish_status by grouping enum values (calendar, published, retry), but leaves 'none' and 'unpublished' unexplained and says nothing about limit or the active-project default.

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 (list) and resource (the project's LinkedIn post drafts) and adds what the records carry (status and publish state). The resource is unambiguous against siblings such as flypost_list_articles, flypost_list_ideas, and flypost_list_media.

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?

The second sentence maps publish_status values to concrete use cases: scheduling calendar, already-published audit, and retry queue. That is real when-to-use guidance, though it offers no explicit exclusions or alternative tools for adjacent needs.

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.