Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

List Brands Tool

list-brands-tool
Read-onlyIdempotent

List the brands configured for a project, newest first. Returns up to 50 per page; follow nextCursor to fetch additional pages. Optionally pass include to load the parent project chain.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "list-brands-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor. Omit on the first call; pass the `nextCursor` value from the previous response to fetch the next page.
includeNoOptional comma-separated related resources to include in the response. Whitelisted: `project`, `project.organization`.
project_idYesThe numeric id of the project whose brands should be listed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description goes beyond them by disclosing the 50-item page cap, the newest-first ordering, and the cursor-following pattern, all useful for correct invocation.

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?

Three short sentences, each carrying distinct information: scope/ordering first, then pagination, then the optional include. No filler or repetition of the title.

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 read-only paginated list tool with fully documented parameters, the description covers scope, ordering, page size, and pagination adequately. With no output schema present, the shape of a returned brand object is left unstated, which is the main residual gap.

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?

Schema coverage is 100%, so the baseline is 3. The description still adds interpretive meaning for `include` ("load the parent project chain") and explains the `nextCursor` -> `cursor` round trip, which helps an agent use the parameters rather than just know their types.

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 names a specific verb and resource ("List the brands configured for a project") and adds ordering ("newest first"), which is more precise than the title. It does not explicitly differentiate itself from siblings like list-projects-tool, but the project-scoped brand 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the project_id scoping and the pagination instructions, giving an agent enough to call it correctly. There is no explicit when-to-use/when-not guidance or reference to alternative tools for related data (e.g., brand analytics or mentions).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pineprompt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources