Skip to main content
Glama
Sign In
meta-ads-mcp

meta-ads-mcp

by fujioka0729
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

meta_ads_api_delete

Send DELETE requests to the Meta Ads API to remove campaigns, ad sets, or ads. Specify the API path and optional query parameters.

Instructions

Meta Ads APIにDELETEリクエストを送信します

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": {
      "path": "<path>"
    },
    "name": "meta_ads_api_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAPIパス（例: /{campaign_id}）
queryNoクエリパラメータ

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior1/5

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

With no annotations, the description must fully disclose behavioral traits. It only says 'sends DELETE request,' adding nothing beyond the name. No mention of authentication, idempotency, side effects, error handling, or return values.

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?

The description is one sentence with no extra words, but it is too brief to be informative. It is concise but under-specified, missing critical details.

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

Completeness1/5

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

The tool lacks an output schema and annotations, and the description does not explain return values, side effects, or what the delete operation entails. It is completely inadequate for a deletion tool.

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?

Schema coverage is 100% with descriptions for both path and query. The description adds no further meaning beyond what the schema provides, resulting in a baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it sends DELETE requests to the Meta Ads API, which is a specific verb+resource. However, it does not differentiate from sibling HTTP method tools beyond the HTTP verb, but the tool name already indicates DELETE.

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?

No guidance on when to use this tool versus alternatives (e.g., get, post). There is no mention of prerequisites, when not to use, or typical use cases. The agent must infer from the HTTP method semantics.

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