Skip to main content
Glama

Claude Plugins Directory

Search Claude plugins

search_plugins
Read-onlyIdempotent

Find Claude plugins by what they do. Every word of the query must appear in the plugin's name, description, category or tags; name matches come first. Filter by category or by source (official = Anthropic and partners in Anthropic's marketplaces).

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": "search_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10, max 25.
queryNoWords to match, e.g. 'code review' or 'sales crm'. Omit to list.
sourceNoDefault all.
categoryNoExact category name from list_categories, e.g. 'Marketing'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuine behavioral detail beyond that: an AND match across name/description/category/tags and name-match-first ordering. It does not describe result shape or pagination, so it adds value but not rich behavioral context.

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?

Three tight sentences with the matching rule front-loaded and no filler. The parenthetical defining 'official' is slightly dense but earns its place by removing ambiguity about the enum value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter, fully documented read-only search with no output schema, the description covers matching semantics, ranking, filtering and the omit-query case. Only the result format and pagination behavior are left unaddressed, which is a minor gap.

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 coverage is 100%, so the baseline is 3; the schema already documents limit defaults, source enum and category examples. The description adds real meaning for query (every word must match, omit to list) and defines 'official' as Anthropic and partners in Anthropic's marketplaces, which goes beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find Claude plugins by what they do') and immediately clarifies the matching model, so an agent knows this is a keyword search over plugin metadata rather than a fetch-by-id tool. Sibling differentiation is only implicit (plugins vs. skills), but the resource is unambiguous.

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?

Explains the retrieval conditions: supply a query to search, omit it to list, and narrow with category or source. It also routes the agent to list_categories for valid category names, which is concrete alternative guidance, though it never states when not to use this tool.

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