Skip to main content
Glama

Market Brew

Discover AI Content Dashboard tools

list_content_tools
Read-onlyIdempotent

Use this when the user asks to discover AI Content Dashboard tools. Returns only data visible to the linked Market Brew account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish a read-only, idempotent, non-destructive, closed-world operation. The description adds the useful constraint that results are limited to data visible to the linked Market Brew account, but provides no further details such as result freshness, ordering, or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences front-load the use case and then state the account-visibility restriction. There is no redundant or distracting wording.

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

Completeness3/5

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

For a zero-argument discovery tool, the use case and access scope support a basic selection and invocation decision. With no output schema, however, the definition does not indicate what each returned entry contains or whether its identifiers can be used with get_content_tool, leaving a clear gap for agents acting on the results.

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?

The tool has no parameters and disallows additional properties, so there are no argument semantics requiring clarification. The account-visibility statement adds relevant invocation context without needing to document inputs.

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?

The description identifies the action and resource by saying the tool is for discovering AI Content Dashboard tools, consistent with its list-oriented name. It does not distinguish this catalog operation from get_content_tool or narrower sibling listings, so its scope is not fully differentiated.

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?

"Use this when the user asks to discover AI Content Dashboard tools" provides an explicit invocation trigger. It offers no when-not guidance or alternative for retrieving an already identified tool, but the intended context is clear.

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