Skip to main content
Glama

list_ideas

Read-only

List the user's ideas (or a teammate's) on the Ideas tab of the active workspace, newest first. Use before save_idea to avoid saving the same idea twice. Pass author to list a teammate's ideas, with the same name you pass to save_idea. Shows each idea's tags, and its references as metadata only (title, url, kind, characters), never their text.

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

NameRequiredDescriptionDefault
limitNoMax results (default 20, max 100)
authorNoOptional: whose ideas to list. A teammate's name, or 'me'. Omit to list yours. Only people who can see everyone's posts may list someone else's.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real behavioral context beyond that. It discloses result ordering (newest first), what is returned per idea (tags), and a non-obvious constraint that references come back as metadata only (title, url, kind, characters) with never their text — something the agent cannot infer from annotations or schema.

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

Conciseness5/5

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

Four sentences, front-loaded with purpose and scope before the workflow hint and return-shape note. Every sentence carries distinct information — dedup warning, author routing, and reference-text exclusion — with no filler.

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

Completeness5/5

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

There is no output schema, and the description compensates by describing the shape of returned items (tags plus references as metadata with title/url/kind/characters). Combined with the ordering note and the permission caveat carried in the schema, an agent has everything needed to call this correctly.

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 all three parameters are already documented in detail, establishing the baseline of 3. The description adds limited value: it reinforces `author` as the teammate-listing switch and cross-references that the name should match what is passed to save_idea, but says nothing about `limit` beyond what the schema states.

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 and resource ('List the user's ideas... on the Ideas tab of the active workspace') plus scope (own vs teammate's) and ordering (newest first). It is clearly distinguishable from siblings save_idea, update_idea, and delete_idea without opening any schema.

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?

Gives an explicit workflow rule: call this before save_idea to avoid duplicate saves, which points the agent at the right alternative at the right moment. It also explains how to switch to a teammate's list via `author`, but offers no explicit when-not-to-use guidance or coverage of the other sibling read tools (list_workspaces, list_members).

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