Skip to main content
Glama

List Clerk SDK snippets

list_clerk_sdk_snippets
Read-onlyIdempotent

List the snippets and bundles clerk_sdk_snippet can return, as Markdown: each bundle's name and description, each snippet's slug, title, description, and tags, and every tag in use.

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_clerk_sdk_snippets"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly list individual snippets with this tag, such as "auth", "organizations", or "billing". Bundles are always listed. Omit to list every snippet.

Output Schema

NameRequiredDescriptionDefault
textYesAvailable Clerk SDK snippets and bundles in Markdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tag / description
      Previous value: -"Filter snippets by tag (e.g. \"auth\", \"organizations\", \"b2b\", \"billing\")"New value: +"Only list individual snippets with this tag, such as \"auth\", \"organizations\", or \"billing\". Bundles are always listed. Omit to list every snippet."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "text": {
      +      "description": "Available Clerk SDK snippets and bundles in Markdown.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "text"
      +  ],
      +  "type": "object"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is low, and the description adds real value by stating the output is Markdown and enumerating what each entry contains (bundle name/description, snippet slug/title/description/tags, all tags in use). It does not discuss result size, pagination, or ordering, which keeps it below 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?

One front-loaded sentence with no filler, and the key framing (what clerk_sdk_snippet can return) comes first. The long enumeration of returned fields is somewhat redundant with the existing output schema but still readable and purposeful.

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 one-optional-parameter, read-only listing tool with a full output schema and strong annotations, the description covers purpose, scope, and output shape adequately. 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.

Parameters3/5

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

Schema description coverage is 100% and the single optional 'tag' parameter is fully documented in the schema, including examples and the important note that bundles are always listed regardless of the filter. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 (List) and resource (snippets and bundles), and explicitly scopes the catalog to what clerk_sdk_snippet can return, which cleanly separates this discovery tool from the retrieval sibling. It also names the serialization format (Markdown) and the fields returned.

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?

The tie to clerk_sdk_snippet implies this is the discovery step before fetching a snippet, but the description never says so outright and gives no explicit when-to-use or when-not-to-use rule. The only conditional guidance ('omit to list every snippet') lives in the schema, not the description.

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