Skip to main content
Glama

Create survey

survey_create

Creates a survey as a DRAFT: its page is not public and no email can ask its questions until it is opened with survey_update. Give it a name and 1 to 30 questions. Returns the survey with each question id; one_click questions (rating, nps, single) can go in an email with campaign_draft. Sends nothing and uses no quota. Requires API key scope: draft.

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": {
      "name": "<name>",
      "questions": "<questions>"
    },
    "name": "survey_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesSurvey name, also used as the page title unless title is set.
introNoShort intro under the heading.
titleNoHeading on the survey page.
questionsYes
thank_you_messageNoShown after someone answers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare a non-readonly, non-destructive, openWorld=false mutation, and the description adds real value beyond that: the draft visibility state, that no email can reference questions until opened with survey_update, that nothing is sent and no quota is consumed, and the required API key scope 'draft'. The only missing piece is whether draft creation is reversible/deletable, which keeps it from a 5.

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?

Front-loaded with the lifecycle fact (DRAFT) that most affects agent decision-making, followed by constraints, return shape, cross-tool compatibility, and auth scope. Every sentence carries distinct information with no 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?

With no output schema, the description correctly covers the return value (survey plus per-question ids), the side-effect profile, the auth scope, and the follow-up call needed to publish. Nothing an agent needs to invoke this correctly 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 80%, so the schema already carries most parameter meaning (question types, scale, options, ids). The description still adds semantics: required name plus 1–30 questions, the fact that each question id is returned for later correlation, and which question types are email-answerable, tying parameters to the campaign_draft workflow.

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 specific verb and resource (creates a survey) plus the crucial lifecycle state (DRAFT), and explicitly contrasts with survey_update for opening it. An agent can distinguish this from survey_update and campaign_draft 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 Guidelines5/5

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

Gives explicit when-to-use context: use this to create, then call survey_update to open it to the public; use campaign_draft only for one_click question types. It also states what the tool will NOT do (no email sent, no quota used), which removes common false assumptions.

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