Skip to main content
Glama
Sign In
X Ads MCP Server

X Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get setup guide

get_setup_guide
Read-onlyIdempotent

Returns step-by-step instructions to connect a specified AI app to the hosted X Ads MCP server by AdKit, including the exact menu path, command, or config snippet.

Instructions

Get the step-by-step instructions to connect one AI app to the hosted X Ads MCP server by AdKit at https://mcp.adkit.so/x-ads. Use this when the user asks how to install, add or connect AdKit in a specific app. Returns Markdown with the exact menu path, command or config snippet. For what the hosted server can do once connected, use list_hosted_tools instead.

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": {
      "app": "<app>"
    },
    "name": "get_setup_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesThe AI app to connect, exactly as listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, closed-world read, so the safety profile is covered. The description adds useful context beyond them by specifying the return format (Markdown containing the exact menu path, command, or config snippet), which matters because no output schema exists. It says nothing about whether guides are static or versioned, but that is a minor omission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it does, when to use it, what it returns, and where to go instead. The routing guidance is front-loaded and no sentence repeats the schema or annotations.

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 single-parameter documentation-lookup tool with no output schema, the description covers action, trigger, return format, and the sibling alternative. Nothing needed to select or invoke it correctly is missing.

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% and the sole parameter is an enum with a description telling the caller to use the listed value exactly as written. The description's phrase 'one AI app' only echoes the schema's intent and adds no syntax or constraint details, so the baseline of 3 applies.

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 names a specific verb and resource — retrieving step-by-step connection instructions for one AI app against the hosted X Ads MCP server at a concrete URL — and scopes it to a single app. It also distinguishes itself from the sibling that answers a different question (list_hosted_tools for capabilities after connection).

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 states the triggering condition explicitly: use when the user asks how to install, add, or connect AdKit in a specific app. It also names the alternative route for a different intent, pointing to list_hosted_tools for what the server can do once connected.

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