DemandBird

update_idea

Edit one idea on the Ideas tab of the active workspace, by the id list_ideas or save_idea gives. Use this, not delete_idea and save_idea, to fix a typo, retag an idea or add a source: the idea keeps its id. Only what you pass changes. content replaces the text, stored verbatim (no AI). tags replaces the idea's tags by name; [] removes them all. references adds source material, NEVER put it in content. All or nothing: if anything is refused, nothing is saved. Only the idea's author or an account admin can edit it.

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": {
      "id": "<id>"
    },
    "name": "update_idea"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The idea's id, from list_ideas or save_idea.
`tags`	No	Optional: the idea's tags by name, replacing the ones it has. [] removes them all. Matched to the workspace's existing tags ignoring case; a name that doesn't exist yet is created if the user may manage tags, otherwise nothing is saved and the reply lists the tags that exist.
`content`	No	Optional: the new text of the idea, up to 5000 characters. Replaces the old text.
`workspace`	No	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.
`references`	No	Optional: source material to add to the idea, stored verbatim and never in `content`. An idea holds at most 20, counting the ones it already has.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

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

AddedOct 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations, it discloses patch semantics ('Only what you pass changes'), id stability, verbatim no-AI storage of content, tag replacement incl. [] clearing, that references are never folded into content, all-or-nothing atomicity, and an authorization rule (author or account admin). The destructiveHint=false annotation is consistent with the 'idea keeps its id' framing; the only missing piece is what the success response looks like.

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-loaded with the action, the id source, and the sibling exclusion before any detail, and the sentences are dense with distinct facts rather than filler. It loses a point for echoing schema-level parameter behaviour in the body when the schema already says it.

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?

For a 5-parameter mutation tool with no output schema, the description covers the things an agent could otherwise get wrong: which fields are replaced vs additive, atomicity on failure, permission requirements, and id preservation. Nothing material needed to invoke it correctly is missing.

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 the parameter meanings, limits and tag-matching rules are already documented in structured fields, and much of the description's parameter prose (content replaces text, tags replace, references never in content) restates that. The 'NEVER put it in `content`' emphasis and the cross-parameter routing hint add a small amount of value over the schema, but not enough to exceed the baseline.

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 ('Edit one idea on the Ideas tab of the active workspace') and anchors the target with the id source ('by the id `list_ideas` or `save_idea` gives'). It explicitly contrasts with the neighbouring delete_idea and save_idea tools, so an agent can distinguish it from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule ('Use this, not delete_idea and save_idea') plus concrete use cases: fixing a typo, retagging, adding a source. It also states the selection-relevant property that the idea keeps its id, which is exactly the condition that separates this from save_idea.

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

All DemandBird 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?