QuestionPunk

Survey Create

survey_create

Create a new, empty draft survey. Returns it as survey_get does: id, versions.current, shareUrl and editorUrl. Add questions next with question_create_bulk, passing versions.current as surveyVersion. To start from a template use template_create_survey_from; to copy a survey, survey_duplicate. Not idempotent: each call creates another survey, so after a timeout check survey_list before retrying. Give the user 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": {
      "title": "<title>"
    },
    "name": "survey_create"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Primary respondent language code (e.g. "en", "ja", "zh-Hans"). Defaults to the account language.
`title`	Yes	Survey title (max 50 characters)
`teamId`	No	Create the survey in this team workspace

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Although annotations already declare idempotentHint=false and destructiveHint=false, the description adds the consequence (each call creates another survey) and the recovery procedure (check survey_list before retrying). It further discloses the return shape (id, versions.current, shareUrl, editorUrl) and the editorial guidance to surface editorUrl as a clickable link, none of which the annotations provide.

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 short sentences, each with a distinct job: what it creates, what it returns, what to do next, what not to confuse it with, and retry safety. The core create action and the return contract are front-loaded; nothing is redundant.

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 three-parameter creation tool with an output schema and annotations, this covers everything an agent needs: purpose, chaining into question_create_bulk, sibling disambiguation, non-idempotent retry handling, and user-facing link presentation. No material gap remains.

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?

All three parameters are fully documented in the schema (100% coverage), including lang examples and the 50-character title limit, so the schema carries the semantic load. The description adds no parameter-level detail beyond the implicit title and the versions.current reference used for chaining. Baseline 3 is appropriate.

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?

"Create a new, empty draft survey" is a specific verb plus resource with the state (empty draft) made explicit. The description also names the two nearest siblings it is not — template_create_survey_from and survey_duplicate — so an agent can route correctly without opening schemas.

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?

It gives the explicit follow-on step (question_create_bulk with versions.current as surveyVersion) and names alternatives for the template and copy cases. The retry procedure after a timeout, checking survey_list rather than re-calling, is a concrete when-not instruction.

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?