QuestionPunk

Survey Update Title

survey_update_title

Destructive

Rename a survey in one of its languages. lang must already be on the survey (survey_get lists them), and for any language other than English auto-translate must be off. Needs version = versions.current from survey_get; a stale version is rejected with WRONG_VERSION, and the result returns the next one as surveyVersion for your next edit. On a published survey the new title is live at once.

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": {
      "surveyId": "<surveyId>",
      "lang": "<lang>",
      "title": "<title>",
      "version": "<version>"
    },
    "name": "survey_update_title"
  }
}

Input Schema

Name	Required	Description
`lang`	Yes	Language code (e.g., "en")
`title`	Yes	New title (max 60 characters)
`version`	Yes	Current survey version: versions.current from survey_get, or the surveyVersion your last edit returned. A stale version is rejected (WRONG_VERSION). The result returns the next one as surveyVersion.
`surveyId`	Yes	Survey ID (from survey_list)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description reinforces this with concrete behavior: stale versions are rejected with WRONG_VERSION, the response returns the next surveyVersion for chaining, and the change goes live immediately on a published survey. This adds real operational context (concurrency contract, live-impact warning) rather than restating the hints.

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?

Four sentences, front-loaded with the action and the two hard preconditions, then the version contract, then the published-survey consequence. Every sentence carries a precondition or a behavioral fact; nothing is filler.

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 destructive, version-guarded mutation with an output schema, the description covers the prerequisite chain (survey_get -> version), failure mode (WRONG_VERSION), and chaining field (surveyVersion) without redundantly explaining return formats. Nothing an agent needs before calling is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds a constraint the schema does not carry: lang must be an existing survey language with auto-translate disabled. Version semantics largely duplicate the schema text, so it earns a 4 rather than a 5.

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?

The opening sentence gives a specific verb and resource ("Rename a survey in one of its languages") and implicitly scopes it away from survey_update_description and survey_update_welcome_screen by naming the title/per-language dimension. An agent can distinguish this from the other survey_update_* siblings without opening the 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?

States explicit prerequisites and exclusions: lang must already exist on the survey (with survey_get as the lookup path), auto-translate must be off for non-English languages, and version must be fresh from survey_get or a prior edit. This is a when-to-use/when-it-fails contract, not just a description.

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

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