QuestionPunk

Survey Duplicate

survey_duplicate

Copy a survey (questions, logic, settings) into a new survey and return the copy as survey_get does, with its id, shareUrl and editorUrl. Pass title to name the copy in the same call. Not idempotent: each call makes another copy, so after a timeout check survey_list before retrying. Give the user the copy's editorUrl as a clickable link.

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>"
    },
    "name": "survey_duplicate"
  }
}

Input Schema

Name	Required	Description	Default
`title`	No	Optional title for the copy, in its primary language (max 60 characters). Without it the copy keeps the original's title.
`surveyId`	Yes	Survey ID to duplicate (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.5/5.0

Behavior5/5

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

Annotations only flag idempotentHint=false; the description converts that into actionable behavior — 'each call makes another copy' — and prescribes a recovery path (verify via survey_list after a timeout). It also specifies the returned identity fields (id, shareUrl, editorUrl) and how to surface editorUrl to the user, which is real context beyond the structured fields.

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 tight sentences, front-loaded with what gets copied, then return shape, then the optional title, then the non-idempotency warning. No restatement of the name or title, and every sentence contributes an operational fact.

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 two-parameter mutation with an output schema, the definition covers the risky behavior (duplicate accumulation), the recovery check, and the return contract. Nothing an agent needs to call it safely is absent.

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 both parameters are already documented, including the 60-character limit and the default-title fallback. The description only adds the framing that title can be set 'in the same call' rather than needing a follow-up; baseline 3 is appropriate when the schema carries the detail.

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?

States a precise verb+resource ('Copy a survey') and enumerates exactly what is carried over (questions, logic, settings) into a new survey. It also anchors the return shape to a known sibling ('as survey_get does'), so the agent can distinguish this from survey_create and survey_get without opening a schema.

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

Usage Guidelines4/5

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

Gives concrete operational guidance: pass title to name the copy in the same call, and after a timeout check survey_list before retrying. What's missing is an explicit exclusion versus survey_create or template_create_survey_from for the blank/from-template cases, leaving that inference to the agent.

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?