Skip to main content
Glama

Get example prompts

get_example_prompts
Read-onlyIdempotent

Retrieve example prompts for using AdKit to report, optimize, and launch campaigns, so users know what to ask the agent first.

Instructions

Get example prompts that work with the hosted AdKit MCP server, 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?

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the return format (a Markdown list) and the topical scope of the prompts. With zero parameters there are no auth, rate-limit, or mutation concerns left unexplained.

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?

Two short sentences with no filler: the first states what the tool returns and its content scope, the second states when to use it. The return format is placed at the end where it is easy to find, and nothing is repeated from the title or annotations.

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, read-only helper with no output schema, the description covers purpose, trigger, and return format, which is enough to call it correctly. A minor gap is whether the returned prompts are generic or tied to specific ad platforms, which would help an agent set expectations before calling.

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 no parameters, so there is no parameter semantics to elaborate and the baseline of 4 applies. The description correctly avoids inventing input details for a no-arg tool.

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 specific verb and resource ("Get example prompts") plus the domain they cover (reporting, optimizing, launching campaigns) and the return format. It is distinguishable from list_ad_platforms and list_hosted_tools, though it does not explicitly separate itself from get_setup_guide or get_skill, which could plausibly serve a similar onboarding intent.

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 a clear trigger condition: use when the user asks what to try first or what to ask the agent. That is a concrete usage context rather than an implied one. It stops short of naming an alternative or stating when not to use it (e.g., versus get_setup_guide for onboarding steps).

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