ProdPad MCP Server

Create ProdPad User Story

prodpad_create_userstory

Create a user story and associate it with a specific idea, including acceptance criteria, to capture product requirements.

Instructions

Create a new user story and associate it with an idea.

Args:

idea_id (string): Numeric ID of the idea to associate with (required)
story (string): The user story text (required)
acceptance_criteria (string): Acceptance criteria for the story

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": {
      "idea_id": "<idea_id>",
      "story": "<story>"
    },
    "name": "prodpad_create_userstory"
  }
}

Input Schema

Name	Required	Description
`story`	Yes	The user story text (e.g. 'As a [persona], I want [feature], so that [benefit]')
`idea_id`	Yes	Numeric ID of the idea to associate with
`acceptance_criteria`	No	Acceptance criteria for the user story

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, covering the safety profile. The description adds no behavioral context beyond the mutation implied by 'Create' – notably it doesn't warn that idempotentHint=false means repeated calls may create duplicate stories, nor discuss permissions or partial-failure behavior.

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

Conciseness3/5

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

The opening purpose sentence is front-loaded and clear, but the subsequent Args list duplicates what the schema already states almost verbatim, adding bulk without new information. Reasonably sized yet partially redundant.

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 simple create tool with full schema coverage and annotations, the definition is minimally adequate – it names the required inputs. It omits what matters most given the crowded sibling set: why an agent should pick this over prodpad_create_idea_userstory, and what the tool returns (no output schema exists to compensate).

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 the schema already documents all three parameters. The Args block merely restates those same descriptions (idea_id, story, acceptance_criteria) without adding format or constraint detail, so the baseline of 3 applies.

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 a specific verb (Create) and resource (user story) plus the scope constraint (associated with an idea), so the operation is unambiguous. However, it does not distinguish itself from the overlapping sibling prodpad_create_idea_userstory, leaving the agent unable to tell the two creation paths apart.

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?

There is no when-to-use/when-not guidance and no mention of the adjacent creation tools (prodpad_create_idea_userstory, prodpad_create_idea). The agent must infer from the name when this path is appropriate versus the sibling.

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