Skip to main content
Glama

Market Brew

Count Content Boosters

count_content_boosters
Read-onlyIdempotent

Use this when the user asks to count Content Boosters. 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": "count_content_boosters"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filters: websiteId, serverHost, title, status, sortBy, sortDir, offset, and pageSize.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / properties / websiteId / anyOf
      Previous value: -[
      -  {
      -    "exclusiveMinimum": 0,
      -    "maximum": 9007199254740991,
      -    "minimum": -9007199254740991,
      -    "type": "integer"
      -  },
      -  {
      -    "pattern": "^[1-9][0-9]{0,17}$",
      -    "type": "string"
      -  }
      -]New value: +[
      +  {
      +    "exclusiveMinimum": 0,
      +    "maximum": 9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "pattern": "^[1-9][0-9]{0,17}$",
      +    "type": "string"
      +  }
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / query / additionalProperties
      Previous value: -{
      -  "type": [
      -    "string",
      -    "number",
      -    "boolean",
      -    "null"
      -  ]
      -}New value: +false
    • addedInput schema / properties / query / properties
      Added value: +{
      +  "offset": {
      +    "maximum": 1000000,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  "pageSize": {
      +    "maximum": 200,
      +    "minimum": 1,
      +    "type": "integer"
      +  },
      +  "serverHost": {
      +    "maxLength": 253,
      +    "type": "string"
      +  },
      +  "sortBy": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "sortDir": {
      +    "enum": [
      +      "asc",
      +      "desc"
      +    ],
      +    "type": "string"
      +  },
      +  "status": {
      +    "maxLength": 80,
      +    "type": "string"
      +  },
      +  "title": {
      +    "maxLength": 2048,
      +    "type": "string"
      +  },
      +  "websiteId": {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  }
      +}
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes one genuine piece of extra context — that results are scoped to data visible to the linked Market Brew account — but says nothing about the response shape (a numeric count) or how filters affect it.

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 with zero filler; the usage trigger is front-loaded and the account-scoping caveat follows. Nothing is repeated or wasted.

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 single optional-filter count operation with rich annotations and a fully described schema, the description covers intent and data-scope adequately. The minor gap is that it does not state the return value is a count computed over the supplied filters, but with no output schema and an obvious result type this is a small omission.

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 description coverage is 100% and the nested query object enumerates every filter (websiteId, serverHost, title, status, sortBy, sortDir, offset, pageSize) in the schema's own description. The tool description adds no parameter meaning beyond that, so the baseline 3 for fully documented schemas applies.

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

Purpose3/5

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

The description states a verb (count) and resource (Content Boosters) that make the operation identifiable, but the wording largely restates the tool name and title rather than adding an independent explanation. It never explicitly contrasts with the sibling list_content_boosters, so an agent must infer the count-vs-list distinction from the name alone.

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?

"Use this when the user asks to count Content Boosters" gives a triggering condition, which is more than nothing. However, there is no when-not guidance and no named alternative (e.g., list_content_boosters when the user wants the records themselves), so usage is only implied.

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