Mark

List Ideas

list_ideas

Read-onlyIdempotent

Lists content ideas: things worth making content about, before or alongside the posts made for them. Filter active (default, not archived), no_posts (active, with no linked post) or archived, optionally by pillar. Each idea has its brief, pillar, angle, persona, buyer question, linked posts counted by stage, last published date, and, when archived, covered (has a published post) or dropped. Ideas never close on their own: only save_idea with archived: true closes one. Returns every tab's count. Does not change anything. Related: save_idea, save_post (ideaId).

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

Input Schema

Name	Required	Description	Default
`filter`	No	active (default), no_posts, or archived.	active
`pillarId`	No	Only ideas with this pillar, from get_brand_context.

Output Schema

Name	Required	Description	Default
`ideas`	Yes
`appUrl`	Yes
`counts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower. The description still adds real value: it explains that ideas never close on their own and only save_idea with archived:true closes one, and that it returns every tab's count. It also states 'Does not change anything,' which is a mild restatement of readOnlyHint but harmless.

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?

Front-loads the purpose, then the filter semantics, then the returned fields, then the mutating-related note. Slightly dense with the long field enumeration, but every sentence earns its place and there is no filler.

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?

Given a 2-param read-only list tool with an output schema present, the description covers interpretation of filter values, the returned fields, archive semantics, and related tools. It does not need to explain return structure since an output schema exists; coverage is strong though not exhaustive.

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 100%, so both parameters (filter, pillarId) are fully documented in the schema itself. The description repeats the filter values without adding syntax or format details beyond what the schema provides, which is the baseline-for-100%-coverage case.

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 (Lists) and resource (content ideas) and immediately defines what an idea is ('things worth making content about, before or alongside the posts made for them'), which meaningfully disambiguates it from sibling post-listing tools like search_posts.

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 filter enum is explained inline (active/no_posts/archived) and the description names related tools (save_idea, save_post). However, it doesn't explicitly state when to prefer this over search_posts or get_post, so routing between listing options is left partly implicit.

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

All Mark tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?