list_clerk_sdk_snippetsList all available Clerk SDK snippets and bundles. Filter by tag to find specific functionality.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Filter snippets by tag (e.g. "auth", "organizations", "b2b", "billing") |
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Available Clerk SDK snippets and bundles in Markdown. |
Changes observed during successful MCP inspections.
Output 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"
+}Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesRemoved value: -falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are all false, so the description carries the burden of behavioral disclosure. It states the tool lists snippets and bundles and can filter by tag, but doesn't disclose return format, pagination, or whether bundles are included by default. It adds some context beyond annotations but not rich behavioral detail.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the main purpose and a clear filter instruction. No wasted words, though it could be slightly more specific about the relationship to the sibling tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple list tool with one optional parameter and an output schema, the description is mostly complete. However, it doesn't clarify whether bundles are separate from snippets, how tags map to results, or any pagination/limits. The output schema exists, so return values are covered, but the tag filtering semantics could be clearer.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents the tag parameter. The description adds the example tags and the filtering behavior, but doesn't add significant meaning beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists all available Clerk SDK snippets and bundles, with a filter by tag. It distinguishes itself from the sibling tool clerk_sdk_snippet by focusing on listing rather than retrieving a single snippet, though it doesn't explicitly name the sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage: use this tool to list snippets and filter by tag. It doesn't explicitly state when to use this tool versus clerk_sdk_snippet, but the listing vs. single-snippet distinction is inferable from the name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.