Skip to main content
Glama
Sign In
Devbook MCP Server

Devbook MCP Server

by leouofa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

devbook_update_prompt

Update a prompt template's title, Markdown body, project assignment, or pinned status by ID, including pin/unpin and pinned-position changes.

Instructions

Update a prompt template's title, Markdown body, project assignment, or pinned status

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": "devbook_update_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the prompt to update
bodyNoUpdated Markdown template content
titleNoUpdated title for the prompt
pinnedNoPin or unpin the prompt
project_idNoReassign to a project ID or null for standalone
pinned_positionNoReorder pinned position
render_markdownNoWhether to return rendered HTML

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It says nothing about whether this is a partial or full replacement update, what happens to omitted fields, permission prerequisites, or whether changes are reversible. For a mutation tool with zero annotation coverage, that is a meaningful gap.

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?

A single efficient sentence with the resource and mutable fields front-loaded and no filler. It could have used its brevity budget to add when-to-use routing instead, but nothing is wasted.

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 7-parameter mutation with no annotations and no output schema, the description covers the main editing surface but leaves partial-update semantics and the pin/reorder overlap unaddressed. An agent could construct a call, but might pick the wrong tool for pin changes.

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 input schema, and the baseline is 3. The description's field list mirrors the schema categories but omits pinned_position and render_markdown, adding no semantics beyond the structured data.

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 and resource ('Update a prompt template') and enumerates the mutable fields, so it is clearly distinguished from create/delete/get siblings. It stops short of differentiating itself from the pin-related siblings it overlaps with.

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?

Usage is only implied by the field list: an agent can infer this is for editing an existing prompt. There is no explicit guidance on when to use this versus devbook_toggle_pin for pinned status or devbook_reorder_pinned for pinned_position, both of which appear to overlap directly with described capabilities.

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