Skip to main content
Glama

Ads MCP Server by AdKit

adkit_help

Read-onlyIdempotent

Read-only reference documentation for the other AdKit tools: field names, accepted values, and per-platform limits. Sections: "manage" (campaigns, accounts, and reporting across Meta, Google, TikTok, Reddit, X, and LinkedIn, plus Pinterest, Microsoft and ChatGPT Ads raw access, and drafts), "integrations" (GA4, Search Console, and Merchant Center), "library" (browse ads, advertisers, and inspiration boards), and "studio" (AI static ad generation). Open a section with path, for example adkit_help({ path: "manage google campaigns create" }), or search it with q, for example adkit_help({ q: "keyword planner" }). It runs nothing and changes nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adkit_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKeyword search across every help path (Manage, Google/Meta/TikTok/LinkedIn/Reddit/X/Microsoft, Library, Studio). Returns the top matching command paths, e.g. q: "keyword planner" finds "manage google research keywords". A nonblank q takes precedence over path and detail. Search here before telling the user a capability is unavailable.
pathNoHelp path, for example "manage meta campaigns" or "library advertisers".
detailNoOptional detail level. Use "full" to include advanced params.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value by clarifying this is documentation only — 'it runs nothing and changes nothing' — which preempts confusion between the 'manage' help section and the adkit_manage execution tool. It stops short of describing the shape of returned documentation.

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 clause, then sections, then two invocation examples, then a closing non-effect statement. The platform enumeration is long but conveys real coverage. No sentence is pure filler, though the platform roster could be tightened.

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 zero-required-parameter documentation tool with full schema coverage and no output schema, this covers what an agent needs: what is behind each section, how to open one, and how to search across all of them. Only the nature of the returned content (prose vs. command paths) is left implicit.

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%, so all three parameters are already documented, including the q-over-path precedence rule and the 'full' enum. The description adds only illustrative path strings that largely duplicate the schema examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource (read-only reference documentation) plus exactly what it contains: field names, accepted values, per-platform limits. The four named sections (manage, integrations, library, studio) and the platform list let an agent distinguish this lookup tool from the executing siblings like adkit_manage and adkit_library without opening any schema.

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?

Gives concrete invocation patterns for both modes — path-based section opening and q-based keyword search — with worked examples. It does not explicitly state when to prefer this over calling adkit_manage directly, but the framing as reference material makes the intent clear. Missing an explicit exclusion, so not a 5.

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.