list_pluginsLists a site's plugins and what can be added (settings_help per kind); without site, those on each site; with plugin_id, that plugin in full (settings, snippet_html, test_steps, recipients, payouts, checkout_fee).
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | The page's <html lang>, e.g. de (one snippet per language) | |
| site | No | ||
| plugin_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| plugins | No |
Changes observed during successful MCP inspections.
Input schema / properties / plugin_id / descriptionRemoved value: -"From list_plugins"Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "plugins": {
+ "type": "array"
+ }
+ },
+ "type": "object"
+}Input schema / properties / lang / descriptionPrevious value: -"The snippet page's <html lang>, e.g. de (one snippet per language)"New value: +"The page's <html lang>, e.g. de (one snippet per language)"Input schema / properties / lang / descriptionPrevious value: -"The <html lang> of the snippet's page (e.g. de); one snippet per language"New value: +"The snippet page's <html lang>, e.g. de (one snippet per language)"Input schema / properties / site / descriptionRemoved value: -"Site name"Input schema / properties / lang / descriptionPrevious value: -"The <html lang> of the page the snippet goes on (e.g. de): snippet_html then speaks it. One snippet per language on a multilingual site"New value: +"The <html lang> of the snippet's page (e.g. de); one snippet per language"Input schema / properties / site / descriptionPrevious value: -"Site name, e.g. brave-otter-4821"New value: +"Site name"Output schema / (root)Previous value: -{
- "additionalProperties": {},
- "properties": {
- "agent_message": {
- "type": "string"
- },
- "confirm_token": {
- "type": "string"
- },
- "error": {
- "description": "On failure (isError): {code, message}"
- }
- },
- "type": "object"
-}New value: +nullInput schema / properties / langAdded value: +{
+ "description": "The <html lang> of the page the snippet goes on (e.g. de): snippet_html then speaks it. One snippet per language on a multilingual site",
+ "type": "string"
+}Input schema / properties / plugin_id / descriptionPrevious value: -"plugin_id (plg_...) from list_plugins or set_plugin"New value: +"From list_plugins"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds mode-dependent behavior and enumerates return contents for the plugin_id case, but does not discuss pagination, limits, or permissions; with an output schema present, the return-field list adds less unique value.
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?
The description is a single front-loaded sentence that conveys several modes efficiently. The semicolon-separated clauses are dense but each carries meaningful information.
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?
Given annotations covering safety and an existing output schema, the description supplies the main missing context: the three query modes and the richer return shape when plugin_id is supplied. Minor gaps around pagination or auth are acceptable here.
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 coverage is only 33%, with site and plugin_id undocumented in the schema. The description compensates well for those two parameters by explaining what omitting site does and what plugin_id retrieves; lang is left to the schema, which does document it.
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?
States a specific verb and resource (lists plugins) and distinguishes modes by site/plugin_id. It does not explicitly contrast with siblings like add_plugin or update_plugin, but the purpose is clear from the description alone.
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 explains the parameter-driven modes (no site = per-site listing, plugin_id = full detail) which implies when each form is useful. It does not say when to use this versus alternatives such as update_plugin or remove_plugin, so guidance remains implicit.
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.