delete_platform_target
Deletes a platform target by its ID. Removes the specified targeting entry from your AdButler account.
Instructions
Delete a platform target
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Platform target ID |
Deletes a platform target by its ID. Removes the specified targeting entry from your AdButler account.
Delete a platform target
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Platform target ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full responsibility for behavioral disclosure. It states the action 'Delete' but does not mention whether deletion is permanent, whether it cascades, or whether special permissions are required. This is a significant gap for a destructive operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short and front-loaded, but it errs on the side of under-specification rather than conciseness. A single sentence can be efficient, yet this one misses opportunities to include behavioral context without adding bulk.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no annotations, no output schema, and only one parameter, the description is insufficient. It does not explain the effects or return behavior, and the sibling set includes many delete_* tools that require clarification. More detail is needed for a complete description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with the single 'id' parameter described as 'Platform target ID'. The description adds no parameter-specific meaning, but the schema already documents the parameter adequately, so the baseline score applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Delete a platform target' is a direct restatement of the tool name, providing no additional context or differentiation from sibling delete tools such as delete_zone or delete_campaign. It identifies the verb and resource but fails to distinguish when this specific target type is meant.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternative delete tools or related platform target operations (list_platform_targets, create_platform_target, update_platform_target). The description offers no exclusions, prerequisites, or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/adbutler/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server