Skip to main content
Glama

List marketing ideas

list_marketing_ideas
Read-onlyIdempotent

Marketing ideas for the business with difficulty, expected impact, time needed, action steps (and which are done) and status. Filter by status (new, in_progress, completed, skipped) or category.

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": {
      "site_id": "<site_id>"
    },
    "name": "list_marketing_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many (default 50)
statusNo
site_idYesThe site, from list_sites
categoryNo
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
      +  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description's added value is disclosing the return shape (difficulty, expected impact, time needed, action steps with done flags, status), which is useful given there is no output schema, but it says nothing about ordering or pagination 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?

Two tight sentences with no filler, and the most informative content (what an idea record contains) is front-loaded. It would be stronger if it opened with an explicit action verb.

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 5-parameter read-only list tool with no output schema, the description covers the return fields and the two filters, which is adequate. It omits maximum page size visibility, default ordering, and any pointer to the sibling that creates or mutates ideas (update_marketing_idea), leaving meaningful gaps.

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 60%: limit, site_id and user_goal are documented in the schema, while status and category have no schema descriptions. The description partially compensates by explaining that status and category are filters and listing the status values, but it does not explain the 13 category values' meaning or how filters combine. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys the resource (marketing ideas for the business) and enumerates the returned fields, but never uses an explicit verb like 'list' or 'retrieve' — the action is only implied by the name. It also makes no attempt to distinguish this from close siblings such as list_growth_content_ideas, list_growth_opportunities, or get_marketing_strategy.

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?

'Filter by status ... or category' describes a capability rather than when to choose this tool. There is no statement of when-not-to-use it, no named alternative, and no prerequisites (e.g. needing a site_id from list_sites, which only appears in the schema).

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