Skip to main content
Glama

Ads MCP Server by AdKit

adkit_setup

Read-onlyIdempotent

Use when the user wants to connect an ad platform (Meta, Google Ads, ...). Returns the link they open to sign in and pick an ad account. Requires projectId from adkit_projects.

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_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoSetup flow to launch. Currently only "manage" is supported for linking ad platforms.
platformNoOptional platform to deep-link directly into. Omit to get the general manage setup links.
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. Changed1 schema field changed
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "meta",
      -  "google",
      -  "tiktok",
      -  "reddit",
      -  "x",
      -  "linkedin",
      -  "microsoft"
      -]New value: +[
      +  "meta",
      +  "google",
      +  "tiktok",
      +  "reddit",
      +  "x",
      +  "linkedin",
      +  "microsoft",
      +  "chatgpt"
      +]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered; the description adds the genuinely non-obvious behavior that this returns an out-of-band link for a human to complete sign-in and account selection. It does not explain what state exists before/after linking or what a failed/expired link looks like, but the human-in-the-loop handoff is the key trait and it is disclosed.

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?

Three short sentences ordered as trigger, return value, prerequisite — the most decision-relevant information leads. Nothing is padded, though the return-value sentence and the prerequisite sentence could be merged without loss.

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?

With 3 params, 100% schema coverage, no output schema and full annotation coverage, the definition supplies the one thing structured fields cannot: that the output is a URL a human must open, plus the projectId source. Missing only the post-link follow-up (check status via adkit_status), which is a minor gap at this complexity.

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 description coverage is 100%, so all three parameters including both enums are already documented in the schema. The description only restates the projectId prerequisite and its adkit_projects origin, adding no new syntax or selection guidance beyond structured data — the baseline 3 applies.

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?

States a concrete action (connect an ad platform) plus a concrete payload (a link the user opens to sign in and pick an ad account). An agent can distinguish this from sibling tools like adkit_projects or adkit_integrations without opening a schema, though it never names a sibling to sharpen the boundary.

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?

"Use when the user wants to connect an ad platform" is an explicit trigger, and "Requires projectId from adkit_projects" names the prerequisite tool to call first. No when-not guidance or explicit alternative for already-connected platforms is offered, which is the only gap.

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.