Skip to main content
Glama
Unilytics MCP Server

Unilytics MCP Server

Official

get_skill

Read-only

Retrieve a saved skill's playbook text, reference and data files, and memory entries by skill ID, paging through long workflows with a cursor.

Instructions

Return one of the user's saved skills: its playbook text, files and how many memory entries it has.

A skill is a step-by-step playbook written by the user, their team (project skills) or Unilytics
(built-in and Unilytics skills). Returns `workflow` (the SKILL.md body), the lists of its
reference_files and data_files, `memory_entries` (learnings saved from earlier runs) and `notes`
(facts such as whether the skill is read-only). A user or project skill also has `owner_display`,
the name of the person who created it ("User" when their account has no name, "Deleted account"
when it was deleted, empty when no person is recorded); `your_role`
(owner, admin or editor can change it; a project viewer can use it, and then `read_only` is true);
and, when the version served
recorded them, `last_edited_by_display` (who saved that version) and `updated_at` (when). A copy of
one of the user's own personal skills has `copied_from` (that skill's id and the version copied),
shown only to that user.

A long workflow comes in pages of up to 40,000 characters as sent (JSON-escaped, so quotes and
line breaks count twice): `workflow_truncated` is true and
`workflow_next_cursor` is set while more steps follow; pass it back as `cursor` for the next page.
An archived skill of the user's answers `archived: true` and `superseded_by`: the skill it was merged into or
replaced by (null when there is none); a merged skill lists `merged_from`.
A very long file list returns its first paths with `<list>_total` (every file stays readable by
path), a long name or description ends in "…", and a field too large to return is null and named
with its size in `omitted_fields`.

Args:
    skill_id: The skill id (e.g. "seo/keyword_research", "unilytics/<name>", "user/<uuid>/<name>"),
        as returned by find_skill or list_skills.
    cursor: workflow_next_cursor from a previous call, for the next page of the workflow.

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_id": "<skill_id>"
    },
    "name": "get_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
skill_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / config
      Removed value: -{
      -  "default": null,
      -  "title": "config",
      -  "type": "string"
      -}
    • addedInput schema / properties / cursor
      Added value: +{
      +  "default": null,
      +  "title": "Cursor",
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. Beyond that the description discloses pagination mechanics (40,000-character pages, workflow_truncated, workflow_next_cursor), truncation sentinels (`<list>_total`, ellipsized names, `omitted_fields` with sizes), archived/superseded_by/merged_from semantics, and role-derived read_only — far more than the annotations provide.

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?

Front-loaded summary sentence, then structured paragraphs on identity/ownership fields, then pagination, then edge cases. Some sentences ramble (the `your_role` and `owner_display` clauses are dense and awkwardly wrapped), but nearly every detail is load-bearing given there is no output schema.

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?

With no output schema, the description must explain return values, and it enumerates the fields, their edge cases (deleted account, null owner, copied_from visibility) and the pagination/truncation contract. Nothing an agent needs to call or interpret a result correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden — and it does: skill_id is documented with three concrete format examples and its provenance, and cursor is defined as workflow_next_cursor from a prior call with its exact purpose.

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?

Opens with a specific verb and resource: 'Return one of the user's saved skills' plus the three things it returns (playbook text, files, memory count). That scope clearly separates it from siblings like read_skill_file (one file) and get_skill_memory (memory entries only).

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?

Tells the agent where the required skill_id comes from ('as returned by find_skill or list_skills') and explains when to re-call with `cursor` to page a long workflow. It stops short of explicitly stating when to prefer this over read_skill_file or get_skill_memory when the agent already has an id.

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