Skip to main content
Glama
doitintl

DoiT MCP Server

Official
by doitintl

delete_insight_results

Destructive

Delete all insights matching a given key along with their associated resource results to clean up batch source data.

Instructions

Manage cloud insights representing recommendations and findings for cloud resources. Deletes all insights matching the specified key from the batch source. This removes the insight and all its associated resource results. For single-insight deletion, use DELETE /source/{sourceID}/insight/{insightKey} instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
insightKeyYes
customerContextNoScope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users.
Behavior4/5

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

Adds behavioral context beyond the annotations: specifies that it removes the insight and all associated resource results. Annotations already indicate destructiveness, but description enriches with scope of deletion.

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

Conciseness3/5

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

Contains a generic first sentence that adds little value. The core action and alternative are clear, but the description could be more direct without the introductory phrase.

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

Completeness2/5

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

Missing important context: no mention of what 'batch source' is, no sourceID parameter, no details on idempotency, errors, or return values. For a destructive operation with no output schema, more completeness is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 50% schema coverage and no description for insightKey, the description fails to add meaning beyond the schema. Only customerContext is described in schema, not in description.

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 clearly states it deletes all insights matching a key from the batch source, and distinguishes from the sibling tool delete_insight_result by mentioning single-insight deletion alternative.

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?

Provides explicit guidance to use the alternative endpoint for single-insight deletion, implying this is for batch deletion, but does not elaborate on when to avoid using this tool.

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

Install Server

Other Tools

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/doitintl/doit-mcp-server'

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