Skip to main content
Glama

create_survey

Create a new, empty survey in your personal workspace or a team, and return its survey_id and draft link. It starts with only its End of Survey screen; questions go in a standard block added with edit_block create.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_survey"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoSurvey title; punctuation and Unicode characters are allowed (default: 'Untitled survey')
team_idNoTeam UUID to create in (default: your personal workspace)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds real behavioral detail beyond that: the survey starts with only an End of Survey screen and no questions, and the call returns a survey_id and draft link.

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?

Two sentences, front-loaded with the action and result, followed by the one non-obvious state detail and next step. No redundant restatement of the name or schema fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema and annotations carry the return shape and safety profile, so the description only needs the initial-state and next-step context, which it supplies. Only the relationship to create_survey_from_version is left unaddressed.

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 coverage is 100%, so both parameters (name, team_id) are already documented with defaults in the schema. The description only restates the personal-workspace-versus-team targeting, adding no syntax or constraint information beyond the schema.

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 (create a new, empty survey) plus where it lands (personal workspace or team) and what it returns. The word 'empty' implicitly separates it from create_survey_from_version, though that sibling is never named.

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 a clear workflow cue: the survey starts with only its End of Survey screen and questions are added via edit_block create. It does not explicitly say when to prefer create_survey_from_version over this, so the routing guidance is slightly incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources