Skip to main content
Glama
JTreadwell1

ProdPad MCP Server

by JTreadwell1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create ProdPad Idea

prodpad_create_idea

Create a new idea in ProdPad with title, description, product, tags, status, and business case details.

Instructions

Create a new idea in ProdPad.

Args:

  • title (string): Idea title (required)

  • description (string): Description (HTML)

  • product_id (string): Product ID or name

  • tags (array): Tag names or IDs

  • status_id (number): Status ID. Use prodpad_list_statuses to find IDs

  • state (string): active, active_public, archived, or unsorted

  • business_case_problem (string): Problem statement

  • business_case_value (string): Value proposition

  • functional (string): Functional spec

  • notes (string): Additional notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTag names or IDs to apply
notesNoAdditional notes (HTML)
stateNoIdea state (default: active)
titleYesIdea title (required unless description is provided)
status_idNoInitial status ID (numeric). Use prodpad_list_statuses to find valid IDs
functionalNoFunctional specification (HTML)
product_idNoProduct ID or name to associate with
descriptionNoIdea description (HTML supported)
business_case_valueNoBusiness case: value proposition (HTML)
business_case_problemNoBusiness case: problem statement (HTML)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/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, so write/non-destructive/non-idempotent behavior is covered structurally. The description adds no behavior beyond that – it doesn't say what is returned, whether unknown tags are auto-created, or how tag name vs tag ID resolution errors surface.

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?

The purpose sentence is front-loaded and the Args list is compact and scannable. Every line maps to a real parameter with no filler prose.

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?

With no output schema, an agent would benefit from knowing what a successful create returns (e.g., the new idea ID for follow-up calls such as prodpad_create_idea_userstory), but the description omits this. Annotations plus full schema coverage make it callable, but return-value context 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 description coverage is 100%, so every parameter is already documented in the schema, and the description largely restates the same field list (HTML formats, enum values, status lookup hint) rather than adding new semantics. Baseline 3 applies when the schema does the heavy lifting.

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+resource ('Create a new idea in ProdPad'), which cleanly separates it from sibling creators like prodpad_create_initiative and prodpad_create_userstory. It does not explicitly name those siblings or state scope boundaries, but the resource is unambiguous.

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

Usage Guidelines3/5

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

The only routing guidance is 'Use prodpad_list_statuses to find IDs' for status_id, which is useful, but there is no when-to-use vs prodpad_create_initiative/other creation tools, and no prerequisite or duplicate-handling guidance. Usage is implied by the tool name rather than explained.

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

Deploy Server

Other Tools