Skip to main content
Glama

Ads MCP Server by AdKit

adkit_manage

Destructive

Manage AND report on Meta, Google, TikTok, Reddit, X, LinkedIn, Microsoft, Pinterest, and ChatGPT Ads.

Reporting & analytics — campaign performance, results, spend, ROAS, impressions, clicks, conversions, CPC/CPA: use entity:"results" (Google also supports action:"placements" and "search-terms"). For advertiser benchmarks, use entity:"benchmarks", a platform, and params.from:"YYYY-MM"; omit to for one month and omit action (Meta, Google, TikTok and LinkedIn). Answers "how are my ads doing" / "what's my spend" / "show campaign performance".

Management — connect project accounts and create, edit, or publish supported ad resources. Pinterest supports account setup and account-scoped raw API access. ChatGPT Ads supports normalized account assignment; its advertiser operations use entity:"platform-api-request".

Coverage differs per platform; the reference for each platform's entities, actions, and field names is adkit_help({ path: "manage " }).

Most mutations create drafts by default; publish:true sends changes live and requires explicit user approval. Use AdKit field names in params (not raw platform fields); pass full request bodies as top-level data. Use platformOverrides for raw fields on supported resources. Unsupported native platform resources and workflows are reachable via the raw platform API: entity:"platform-api-request" action:"mutate" (project opt-in); adkit_feedback is the channel for reporting these AdKit gaps. File uploads: entity:"media" action:"request_upload_url" → PUT the bytes → reference the returned uploadId. For creatives/variants/images inside an ad set, use entity:"ads".

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": {
      "entity": "<entity>"
    },
    "name": "adkit_manage"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional entity identifier for single-item actions like get, update, disconnect, pages, pixels, and similar routes. Do not use this for drafts publish/delete; those require ids[].
idsNoDraft batch identifier list. Required for entity: "drafts" with action: "publish" or "delete", even for a single draft. Each array item must be exactly one draft ID. Good: ["id1","id2"]. Bad: ["id1,id2"].
dataNoTop-level AdKit request body merged over params for mutation requests after request shaping.
actionNoAction to run on the entity, for example list, get, create, update, delete, or publish. Not needed for benchmarks reports. The per-entity reference is adkit_help({ path: "manage <platform> <entity>" }).
entityYesEntity name. Common: campaigns, adsets, ads, accounts, media, research, results, benchmarks, drafts, platform-api-request. The per-platform reference is adkit_help({ path: "manage <platform>" }).
paramsNoFree-form request params. GET requests send params as query. Mutations send params as body fields by default, but some Google mutations route IDs like accountId/adGroupId/campaignId into query when the REST route expects them there. Batch/full AdKit bodies belong in top-level data.
publishNoOptional publish flag for create flows that support immediate execution.
platformNoAd platform for the requested entity and action.
accountIdNoAd account to act on for the selected platform. Auto-resolved when the project has exactly one account on that platform; REQUIRED when multiple are connected. Get available ids from adkit_status or the platform accounts entity.
projectIdNoRequired. Get from adkit_projects. Auto-resolves only for single-project users.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "meta",
      -  "google",
      -  "tiktok",
      -  "reddit",
      -  "x",
      -  "linkedin",
      -  "microsoft",
      -  "chatgpt"
      -]New value: +[
      +  "meta",
      +  "google",
      +  "tiktok",
      +  "reddit",
      +  "x",
      +  "linkedin",
      +  "microsoft",
      +  "pinterest",
      +  "chatgpt"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Required except for benchmarks reports, which take no action. Actions and entity-specific requirements are documented in adkit_help."New value: +"Action to run on the entity, for example list, get, create, update, delete, or publish. Not needed for benchmarks reports. The per-entity reference is adkit_help({ path: \"manage <platform> <entity>\" })."
    • changedInput schema / properties / entity / description
      Previous value: -"Entity name. Common: campaigns, adsets, ads, accounts, media, research, results, benchmarks, drafts, platform-api-request. Platform-specific entities are listed under adkit_help({ path: \"manage <platform>\" })."New value: +"Entity name. Common: campaigns, adsets, ads, accounts, media, research, results, benchmarks, drafts, platform-api-request. The per-platform reference is adkit_help({ path: \"manage <platform>\" })."
  3. Changed1 schema field changed
    • changedInput schema / properties / action / description
      Previous value: -"Required except for benchmarks, which takes no action. Action: list, get, create, update, delete. Entity-specific actions are listed under adkit_help({ path: \"manage <platform>\" })."New value: +"Required except for benchmarks reports, which take no action. Actions and entity-specific requirements are documented in adkit_help."
  4. Changed3 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Action: list, get, create, update, delete. Entity-specific actions are listed under adkit_help({ path: \"manage <platform>\" })."New value: +"Required except for benchmarks, which takes no action. Action: list, get, create, update, delete. Entity-specific actions are listed under adkit_help({ path: \"manage <platform>\" })."
    • changedInput schema / properties / entity / description
      Previous value: -"Entity name. Common: campaigns, adsets, ads, accounts, media, research, results, drafts, platform-api-request. Platform-specific entities are listed under adkit_help({ path: \"manage <platform>\" })."New value: +"Entity name. Common: campaigns, adsets, ads, accounts, media, research, results, benchmarks, drafts, platform-api-request. Platform-specific entities are listed under adkit_help({ path: \"manage <platform>\" })."
    • changedInput schema / required
      Previous value: -[
      -  "entity",
      -  "action"
      -]New value: +[
      +  "entity"
      +]
  5. Changed2 schema fields changed
    • changedInput schema / properties / accountId / description
      Previous value: -"Ad account to act on: Meta act_ id, Google customerId, TikTok advertiserId, Reddit ad account id, or X ad account id. Auto-resolved when the project has exactly one account on that platform; REQUIRED when multiple are connected. Get the available ids from adkit_status."New value: +"Ad account to act on for the selected platform. Auto-resolved when the project has exactly one account on that platform; REQUIRED when multiple are connected. Get available ids from adkit_status or the platform accounts entity."
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "meta",
      -  "google",
      -  "tiktok",
      -  "reddit",
      -  "x",
      -  "linkedin",
      -  "microsoft"
      -]New value: +[
      +  "meta",
      +  "google",
      +  "tiktok",
      +  "reddit",
      +  "x",
      +  "linkedin",
      +  "microsoft",
      +  "chatgpt"
      +]
  6. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Against annotations that flag destructiveHint=true and openWorldHint=true, the description discloses the key safety behavior: most mutations create drafts by default and publish:true sends changes live and requires explicit user approval. It also discloses that raw platform API mutation is project opt-in, that coverage differs by platform, and that AdKit field names rather than raw platform fields must be used with platformOverrides for raw fields — all context the annotations cannot convey.

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?

It is long but sectioned with em-dash headers (Reporting & analytics, Management) and front-loads the two main jobs before routing details. Nearly every sentence carries a distinct routing rule, though the platform-roll-call in the first line and the trailing upload/creative instructions make it denser than needed.

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

Completeness5/5

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

For a 10-parameter, multi-platform umbrella tool with no output schema, the description covers job routing, draft-versus-live mutation semantics, field-naming conventions, the raw-API escape hatch, the three-step upload flow, and the metrics available in reports. Remaining detail is explicitly delegated to adkit_help({ path: "manage <platform>" }), which is the correct place for it.

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?

Schema coverage is 100%, so the baseline is 3; the description earns a notch more by adding meaning the schema does not restate — params.from:"YYYY-MM" with to omitted for a single month, omitting action for benchmarks, publish:true for immediate execution, and platformOverrides for raw fields. It still leaves the free-form params/data contract to the per-platform help reference rather than explaining it here.

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 opening line names the verb pair (manage/report) and the exact resource set (nine ad platforms), and the two section headers split reporting (entity:"results", entity:"benchmarks") from management (entity:"drafts", entity:"platform-api-request", entity:"media", entity:"ads"). It is clearly distinguishable from adkit_help and adkit_feedback, but the sheer breadth of entities left to the per-platform reference keeps it from being a crisp single-purpose statement.

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?

Guidance is concrete: use entity:"results" for performance/spend/ROAS, entity:"benchmarks" with params.from for advertiser benchmarks, entity:"platform-api-request" for unsupported native resources, entity:"media" for uploads, entity:"ads" for creatives, and adkit_feedback for reporting AdKit gaps. It never states when this tool is the wrong choice (e.g. versus adkit_status or adkit_setup for non-CRUD work), so the alternatives are named but the negative boundaries are incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.