Skip to main content
Glama
Sign In
X Ads MCP Server

X Ads MCP Server

by adkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get example prompts

get_example_prompts
Read-onlyIdempotent

Provides ready-to-use X Ads prompts for reporting, optimizing, and launching campaigns, helping users discover what to ask the agent first. Returns a Markdown list.

Instructions

Get example prompts that work with the hosted X Ads MCP server by AdKit, such as reporting, optimizing and launching campaigns. Use this when the user asks what to try first or what to ask the agent. Returns a Markdown list.

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": "get_example_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by stating the return format ('Returns a Markdown list'), which is the main thing an agent needs to know for a no-input content tool and which is not present in any structured field.

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 short sentences, front-loaded with what the tool returns, followed by the trigger condition and the output format. Nothing is repeated from the name or annotations, and there is no filler.

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-parameter, low-risk tool with no output schema, the description covers what it does, when to call it, and the shape of the return value. The only meaningful gap is that it does not clarify how it relates to the other content siblings (get_faq, get_setup_guide), which is the one real routing ambiguity.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The empty schema and the description agree that no input is needed.

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 description names a concrete verb and resource ('Get example prompts') and scopes the content to the hosted X Ads MCP server by AdKit, with concrete examples of the prompt categories (reporting, optimizing, launching campaigns). It stops short of distinguishing this from other content-style siblings such as get_faq or get_setup_guide.

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?

It gives a clear trigger: 'Use this when the user asks what to try first or what to ask the agent.' That is a recognizable intent an agent can match on. It does not say when not to use it or point to a sibling for adjacent intents.

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