Skip to main content
Glama

Edge Skills: playlists

manage_collection

Only when the user asks about Edge playlists (formerly collections): follow, unfollow or list ones they follow ("follow playlist federico/comms", a getedge.cc/playlists/ link), or make and edit their own ("make a playlist of the skills I used for X", "add Y to my playlist", "show my playlists", "make it public"). A playlist is a named set of 2 to 20 skills for one job. To create one, pass title, a one-line description and skills as owner/repo@skill exactly as find_skill printed them, in the order to use them; update takes the full new list (add, remove and reorder are one save). New playlists are unlisted (link only). publish makes one public only when all its skills pass Edge's scan, its text has no personal data and 3 signed-in people besides the creator follow it. Never call it on your own initiative. Reply with the returned line.

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": {
      "action": "<action>"
    },
    "name": "manage_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNocreate/update: the playlist's title
actionYesfollow/unfollow/list followed playlists; create/update/delete/mine/publish/unpublish the user's own
skillsNocreate/update: owner/repo@skill ids, in order
descriptionNocreate/update: one line on what it is for
collection_idNoThe playlist's name (federico/comms), id or getedge.cc/playlists/ link; required except for list, mine and create

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations supply only idempotentHint=false, so the description carries most of the burden and does well: it discloses that new playlists are unlisted/link-only, that update replaces the whole list rather than patching, and the three publish preconditions (scan pass, no personal data, 3 signed-in non-creator followers). It stops short of stating permissions needed, what delete destroys irreversibly, or failure modes when a skill fails the scan.

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-loads the when-to-use gate, then creation semantics, then the publish constraints, then the reply instruction — a sensible ordering with no filler sentences. It is dense with quoted examples, which costs some scanability but each clause conveys distinct operational detail.

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 5-parameter, 9-action tool with no output schema, the description covers scope, the id format source, replacement semantics, visibility defaults, publish gating, and even the expected reply shape ("Reply with the returned line"). Nothing an agent needs to invoke it correctly appears 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%, so the baseline is 3, but the description adds genuine meaning beyond the schema: skills must be owner/repo@skill exactly as find_skill printed them, in intended usage order, and update requires the full replacement list (add/remove/reorder are one save). That ordering and full-replacement semantics are not in the schema descriptions.

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?

Names specific verbs (follow, unfollow, list, create, edit, publish) bound to a specific resource (Edge playlists, formerly collections), and anchors each in a concrete user utterance example. An agent can distinguish this from find_skill or list_starred without opening any schema.

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

Usage Guidelines5/5

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

Opens with an explicit eligibility gate ("Only when the user asks about Edge playlists") and closes with a hard prohibition ("Never call it on your own initiative"). It also names the upstream dependency for ids (find_skill), which routes the agent correctly between tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources