Skip to main content
Glama

Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads

by io.github.adkit
OverviewDiscussionsAdmin

adkit_library

Browse 1M+ ads from thousands of advertisers across Meta, Google, and LinkedIn. Keep a per-project watchlist of advertisers and save ads to shareable inspiration boards. For advertiser list/search, params.scope is library (default, all advertisers) or watchlist (the selected project's My Watchlist). Create and fill boards before setting shareEnabled: true through boards update, and only enable sharing when the user explicitly asks. The user's own campaigns live in adkit_manage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoEntity identifier. Required for get, track, untrack, boards get, boards update, and boards add-ads.
actionYeslist, search, get, and similar only read. add and track put an advertiser on the selected project's watchlist; untrack takes it off that list and leaves the advertiser and its ads in the library. Boards: create starts an empty board, update edits its name, description, color, or sharing, and add-ads adds library ads to it.
entityYesLibrary entity to query.
paramsNoFree-form request params. Sent as query for GET requests and as body fields for mutations.
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 / action / description
      Previous value: -"Library action to execute. For advertisers, track/untrack changes the selected project watchlist. For boards, list/get reads the selected project, create/update changes board metadata, and add-ads saves selected library ads."New value: +"list, search, get, and similar only read. add and track put an advertiser on the selected project's watchlist; untrack takes it off that list and leaves the advertiser and its ads in the library. Boards: create starts an empty board, update edits its name, description, color, or sharing, and add-ads adds library ads to it."
  2. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Library action to execute. For advertisers, track/untrack changes the selected project watchlist. For boards, create/update changes board metadata and add-ads saves selected library ads."New value: +"Library action to execute. For advertisers, track/untrack changes the selected project watchlist. For boards, list/get reads the selected project, create/update changes board metadata, and add-ads saves selected library ads."
    • changedInput schema / properties / id / description
      Previous value: -"Entity identifier. Required for get, track, untrack, boards update, and boards add-ads."New value: +"Entity identifier. Required for get, track, untrack, boards get, boards update, and boards add-ads."
  3. Changed4 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Library action to execute. For advertisers, track/untrack adds/removes an existing advertiser from the selected project watchlist; add requires a website or ad library URL and tracks the advertiser. For a name, search first, then track its ID."New value: +"Library action to execute. For advertisers, track/untrack changes the selected project watchlist. For boards, create/update changes board metadata and add-ads saves selected library ads."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "list",
-  "search",
-  "get",
-  "similar",
-  "add",
-  "track",
-  "untrack"
-]New value: +[
+  "list",
+  "search",
+  "get",
+  "similar",
+  "add",
+  "track",
+  "untrack",
+  "create",
+  "update",
+  "add-ads"
+]
    • changedInput schema / properties / entity / enum
      Previous value: -[
-  "advertisers",
-  "ads"
-]New value: +[
+  "advertisers",
+  "ads",
+  "boards"
+]
    • changedInput schema / properties / id / description
      Previous value: -"Entity identifier. Required for get, track, and untrack; track/untrack change watchlist membership for the selected project only."New value: +"Entity identifier. Required for get, track, untrack, boards update, and boards add-ads."
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds genuine behavioral context beyond the annotations: the sharing action is gated on explicit user intent, and create/add-ads have ordered prerequisites. It does not discuss rate limits or return shape, but the added sharing constraint is meaningful.

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?

Purpose is front-loaded in the first sentence, followed by capability, scope semantics, and a safety caveat. It is dense but every sentence carries distinct information; the middle sentences are somewhat packed but not wasteful.

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 multi-entity, multi-action tool with a free-form params object and no output schema, the description covers the main entity/action split, the boards workflow, and the sibling boundary. Remaining gaps (e.g., search vs list distinction, similar) are minor since the schema's action enum documents those.

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%, giving a baseline of 3, and the description exceeds that by explaining params.scope values (library vs watchlist) that the free-form params object (additionalProperties: true) leaves undefined. That is real meaning beyond the schema, though it covers only one of the nested params.

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 a specific verb and resource ('Browse 1M+ ads from thousands of advertisers across Meta, Google, and LinkedIn') and layers on the watchlist and boards capabilities. It explicitly names the sibling boundary by pointing to adkit_manage for the user's own campaigns, so an agent can distinguish this library-browsing tool from management tools without opening schemas.

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

Usage Guidelines5/5

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

It gives explicit when-to-use rules: params.scope library vs watchlist, and the sequencing rule 'Create and fill boards before setting shareEnabled: true through boards update.' It also states an exclusion ('only enable sharing when the user explicitly asks') and routes own campaigns to adkit_manage.

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

All Ads Manager by AdKit: Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources