Skip to main content
Glama
Sign In
gpsem

gpsem

by puples
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Lister les idées de contenu

listContentIdeas
Read-onlyIdempotent

Retrieve content ideas with their status (to write, writing, refused) and associated page URLs for a given site, enabling quick review and prioritization of pending content tasks.

Instructions

Lister les idées de contenu — Idées avec leur statut (to_write, writing, refused) et la page produite. — (GET /sites/{siteId}/contenus)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteId": "<siteId>"
    },
    "name": "listContentIdeas"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoRecherche
pageNoPage (défaut 1)
limitNoNombre de résultats (≤ 500, défaut 100)
siteIdYesID site encodé (hashid)
sourceNourl ou expression
statusNo0 refusée, 1 à rédiger, 2 en rédaction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that the result includes status and the produced page, which is mild additional context, but it does not disclose response shape, pagination metadata, or ordering behavior.

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?

The description is short and front-loaded with the core purpose, followed by the returned fields and the endpoint. The endpoint annotation is arguably redundant with the tool name, but it does not bloat the text.

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?

With six parameters and no output schema, the description is too thin. It mentions the returned status and page but does not explain filtering behavior, pagination semantics, or the actual response structure. An agent would still need to infer important call-level details.

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 description coverage is 100%, so each parameter is already explained (q, page, limit, siteId, source, status). The description adds no parameter-level detail beyond the schema; the baseline of 3 is appropriate because the schema carries the full parameter burden.

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?

The description clearly identifies the action ('Lister') and resource ('idées de contenu'), and adds that results include each idea's status and the produced page. This distinguishes it from the singular getContentIdea and from writeContentIdea, which are the main sibling alternatives.

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?

There is no explicit guidance about when to use this tool versus siblings like getContentIdea or writeContentIdea. The description implies a listing use case but never states exclusions or alternatives, so an agent must infer when this is the right choice.

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

Deploy Server

Other Tools