Skip to main content
Glama

List ideas & concepts

flypost_list_ideas
Read-only

List the project's content bank items (ideas and developed concepts) with stage, format and asset state.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
stageNo
project_idNoProject id; omit for the active project.
target_formatNoThe post format the idea targets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful return-shape context ("with stage, format and asset state") that no output schema provides. It does not disclose ordering, default page size, or whether archived/rendered items are included.

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?

One compact, front-loaded sentence with no filler; the resource comes first and the returned attributes trail it. "Asset state" is the only slightly opaque phrase, but it does not cost readability.

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 read-only list tool with annotations and no output schema, the essentials are present but pagination behaviour, default limit, and inclusion/exclusion of archived items are left unstated across both schema and description. Adequate to call correctly, not complete enough to predict results.

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%: project_id carries its own description, and the two enum params (stage, target_format) are only self-documented by their enum values. The description's mention of "stage, format" loosely maps to those filters but adds no filtering semantics, and the limit parameter is never addressed. Baseline 3 applies given partial schema support.

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?

Uses a specific verb ("List") plus a scoped resource ("project's content bank items (ideas and developed concepts)"), and the parenthetical separates it from sibling lists like flypost_list_articles and flypost_list_drafts. It stops short of naming which sibling to use instead, but the resource 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 Guidelines2/5

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

The description says what is listed but never states when to choose this over flypost_brainstorm_ideas or flypost_list_articles, nor any prerequisite (e.g. a project must have content-bank items). The browsing use case is only inferable from the noun phrase, so it falls short of clear 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.