Skip to main content
Glama

List hosted tools

list_hosted_tools
Read-onlyIdempotent

Shows what an agent can do with ad accounts after connecting by listing hosted AdKit tools and their functions in a Markdown table, without calling them.

Instructions

List the tools of the hosted AdKit MCP server (https://mcp.adkit.so), with one line on what each tool does. Use this to explain what an agent can do with ad accounts after connecting, such as creating campaigns, pulling performance or uploading media. Returns a Markdown table. It does not call those tools; they only run on the hosted server.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is largely covered. The description adds two things annotations cannot: the return format (a Markdown table) and the crucial clarification that it does not invoke the listed tools. No auth or latency details, but little more is needed for a read-only catalog call.

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 sentences, front-loaded with what the tool returns, then when to use it, then the critical boundary about not calling the tools. Every clause carries information; the campaign/performance/media examples make the value concrete without padding.

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 zero-parameter, read-only listing tool with no output schema, the description covers what it returns (Markdown table), what the rows mean (one line per tool), and what it does not do (execute hosted tools). Nothing an agent needs in order to call it correctly is missing.

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 empty object schema is self-explanatory. Baseline for a parameterless tool applies; no compensating text is required.

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: "List the tools of the hosted AdKit MCP server" plus a pointer to the server URL, and adds scope ("with one line on what each tool does"). The closing line ("It does not call those tools; they only run on the hosted server") separates it from any tool that would actually act on ad accounts.

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 this to explain what an agent can do with ad accounts after connecting" gives a clear situational trigger and names concrete example categories. It stops short of naming an alternative sibling (e.g. get_skill or get_setup_guide) or stating when not to use it, so it is strong context without full routing.

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