Skip to main content
Glama
dscovr

surveymonkey-mcp

by dscovr

surveymonkey_delete_question

Delete a question from a survey page permanently. Provide survey, page, and question IDs to remove it—irreversible action.

Instructions

Deletes a question from a survey page. WARNING: irreversible operation.

Args: survey_id: Survey ID. page_id: Page ID. question_id: Question ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYes
survey_idYes
question_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the safety burden. The prominent 'WARNING: irreversible operation' explicitly flags that this is a destructive, permanent action. It does not mention permissions or effects on response data, but the key behavioral risk is disclosed.

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?

The description is compact and front-loaded: the action comes first, followed by the irreversible warning, then a minimal args list. Every line earns its place with no filler.

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?

For a simple delete operation with three required IDs, the definition provides the essential information: what is being deleted, where it lives, and required parameters. The only gaps are the lack of return-value details and explicit consequences beyond irreversibility, which are minor for this operation.

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?

The Args block names all three parameters and labels them as Survey ID, Page ID, and Question ID. This slightly clarifies their roles, though it mostly restates the schema property titles and adds little detail about formats or how the IDs relate.

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 states 'Deletes a question from a survey page,' which clearly identifies the action, resource, and scope. This distinguishes it from sibling tools like delete_survey and delete_page without ambiguity.

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

Usage Guidelines3/5

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

Usage is implied by the verb and object: use this tool when removing a question from a survey page. However, the description does not explicitly say when to use it versus alternatives, nor does it provide any when-not-to-use guidance.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dscovr/surveymonkey-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server