Skip to main content
Glama

update_idea

Modify existing ideas by updating titles, summaries, statuses, RICE scores, or destinations to maintain accurate product feedback records.

Instructions

Update an existing idea. Can update title, summary, status, scores, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ideaIdYesThe unique ID of the idea to update
titleNoNew title
summaryNoNew summary
statusNoNew status
destinationNoNew destination
riceReachNoRICE reach score (0-10)
riceImpactNoRICE impact score (0-3)
riceConfidenceNoRICE confidence (0-1)
riceEffortNoRICE effort in person-months

Implementation Reference

  • Schema definition for the 'update_idea' tool in proxyTools.ts. Note that it appears to be defined but not yet integrated into the main MCP handler in src/mcp/handler.ts.
    {
      name: 'update_idea',
      description: 'Update an existing idea. Can update title, summary, status, scores, etc.',
      inputSchema: {
        type: 'object' as const,
        properties: {
          ideaId: {
            type: 'string',
            description: 'The unique ID of the idea to update',
          },
          title: { type: 'string', description: 'New title' },
          summary: { type: 'string', description: 'New summary' },
          status: {
            type: 'string',
            enum: ['new', 'accepted', 'rejected', 'snoozed', 'expired'],
            description: 'New status',
          },
          destination: {
            type: 'string',
            enum: ['github', 'linear', 'jira', 'azure-devops', 'zendesk'],
            description: 'New destination',
          },
          riceReach: { type: 'number', description: 'RICE reach score (0-10)' },
          riceImpact: { type: 'number', description: 'RICE impact score (0-3)' },
          riceConfidence: { type: 'number', description: 'RICE confidence (0-1)' },
          riceEffort: { type: 'number', description: 'RICE effort in person-months' },
        },
        required: ['ideaId'],
      },
      annotations: { readOnlyHint: false, destructiveHint: false, openWorldHint: true },
      _meta: { 'openai/visibility': 'public' },
    },
Behavior3/5

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

Annotations already cover mutation (readOnlyHint=false) and external world (openWorldHint=true). The description adds context by grouping the four RICE parameters under 'scores', but does not clarify partial update semantics, non-destructive nature, or what the destination field implies.

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 concise sentences with front-loaded action. The 'etc.' placeholder prevents a perfect score as it wastes opportunity to mention critical parameters like 'destination' or partial update capability.

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?

Adequate for identifying the tool's basic function but incomplete for a 9-parameter mutation tool with external integrations. Missing: partial update semantics, the significance of the destination enum (GitHub, Linear, etc.), and differentiation from normalize_idea.

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 has 100% description coverage, establishing a baseline of 3. The description adds semantic value by conceptually grouping riceReach, riceImpact, riceConfidence, and riceEffort as 'scores', but completely omits mention of the 'destination' parameter despite its significance for external integrations.

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

Purpose4/5

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

States specific verb (Update) and resource (idea) and lists key updatable fields (title, summary, status, scores). However, it fails to distinguish from sibling 'normalize_idea' which could also modify ideas, and uses vague 'etc.' rather than mentioning the destination integration capability.

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?

Provides no guidance on when to use this tool versus alternatives like 'normalize_idea' or 'create_ticket'. Does not mention prerequisites (e.g., needing an ideaId from get_idea) or that partial updates are supported since only ideaId is required.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Startvest-LLC/idealift-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server