Skip to main content
Glama

Get agent skill

get_skill
Read-onlyIdempotent

Retrieve full step-by-step instructions for an AdKit agent skill—setup, launch, analyze, spy, or studio—to follow the correct ad workflow and complete that job.

Instructions

Get the full instructions of one AdKit agent skill (SKILL.md): setup connects ad accounts, launch creates campaigns, analyze pulls performance, spy researches competitor ads, studio generates creatives. Use this to follow AdKit's workflow for that job step by step. Returns Markdown.

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": {
      "skill": "<skill>"
    },
    "name": "get_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillYesThe skill to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes beyond them by disclosing the return format ("Returns Markdown") and the content scope of SKILL.md. It does not mention size or truncation behavior, which keeps it short of a 5.

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?

The core action is front-loaded in the first clause, with the skill inventory and return format following. Three sentences with little waste, though the parenthetical domain list is dense and slightly buries the return-format note at the end.

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, fully described read tool with no output schema, the description covers what it returns (Markdown), what each parameter value yields, and how the result should be used. 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?

Schema coverage is 100% with a self-describing enum, so the baseline is 3; the description earns extra credit by explaining what each of the five opaque enum values actually does (setup connects accounts, spy researches competitors, studio generates creatives), which the schema's "The skill to read." does not convey.

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 ("Get the full instructions of one AdKit agent skill (SKILL.md)") and enumerates the five skill domains, so an agent can tell it apart from get_setup_guide or get_example_prompts without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use this to follow AdKit's workflow for that job step by step" gives an implied context for calling it, but there is no explicit when-not guidance and no routing against the near-overlapping siblings get_setup_guide and get_example_prompts.

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