Skip to main content
Glama
Sign In
surveymonkey-mcp

surveymonkey-mcp

by dscovr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

surveymonkey_create_collector

Create a survey collector for weblink, email, SMS, or popup distribution. Set status, thank-you message, close date, redirect URL, and multiple response options.

Instructions

Creates a new collector for a survey.

Args: survey_id: Survey ID. payload: Collector definition. Structure: { "type": "weblink", (required: "weblink", "email", "sms", "popup") "name": "Collector name", (optional) "status": "open", (optional: "open" | "closed") "thank_you_message": "...", (optional) "close_date": "2026-12-31", (optional — ISO 8601 date) "redirect_url": "https://...", (optional — redirect after completion) "allow_multiple_responses": false (optional) }

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": {
      "survey_id": "<survey_id>",
      "payload": "<payload>"
    },
    "name": "surveymonkey_create_collector"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
survey_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states that a collector is created and gives payload constraints, but it does not disclose permissions, side effects, rate limits, or what the created collector contains or returns. This is a meaningful transparency gap for a write operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with the primary purpose, followed by a compact parameter breakdown. The JSON example is warranted and earns its place, though the 'optional' notation repeated per field adds slight redundancy.

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

Completeness3/5

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

It adequately explains the request payload, and an output schema exists, so return-value documentation is not required. However, it lacks usage context and behavioral caveats for a creation endpoint with a nested payload, making it complete for parameter details but not for decision-making context.

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?

The input schema has 0% description coverage, so the description must compensate. It documents survey_id and defines the payload object with a required type enum, optional fields, status values, ISO date format, and boolean field, which adds substantial meaning beyond the bare schema.

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 description opens with 'Creates a new collector for a survey,' giving a specific action and resource with its parent entity. This clearly distinguishes it from sibling tools like update_collector, delete_collector, and list_collectors.

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

Usage Guidelines2/5

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

There is no explicit guidance about when to use this tool versus update_collector or delete_collector, and no conditions for choosing among collector types such as weblink, email, sms, or popup. The intended usage must be inferred from the name and the verb 'creates.'

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

Deploy Server

Other Tools