content-engine-mcp

Overview Schema Source Related Servers Discussions Admin

list_seeds

Lists content seeds from your local project, optionally filtered by kind or status, so you can review active, killed, or developed ideas before drafting.

Instructions

List seeds, optionally filtered.

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

Input Schema

Name	Required	Description	Default
`kind`	No
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: no mention of result ordering, pagination, caps on returned items, or what an unfiltered call returns. Only the existence of optional filtering is conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The single clause is front-loaded and free of waste, but it is under-specified rather than concise — the same brevity could have carried one sentence on filtering or sibling routing at no cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No annotations, no output schema, and zero parameter documentation mean the description is the only source of behavioral detail, and it supplies almost none. For a listing tool with two enum filters this is materially incomplete.

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

Parameters2/5

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

Schema description coverage is 0% and both parameters (kind, status) are enum-only with no prose meaning. The description never names either parameter or explains how the enum values (e.g. active/killed/developed) affect results, so it fails to compensate for the schema gap.

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 gives a clear verb and resource ("List seeds") plus a scope hint ("optionally filtered"), so an agent immediately knows the operation. It does not, however, distinguish this from the sibling search_seeds or get_seed, leaving the agent to guess which retrieval tool fits.

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?

"Optionally filtered" implies filters may be supplied but gives no when-to-use guidance, no conditions selecting this over search_seeds, and no note on what happens with no filters. The agent is left to infer everything about applicability.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.