Skip to main content
Glama

Market Brew

Get Launchpad content-gap statistics

get_launchpad_stats
Read-onlyIdempotent

Use this when the user asks to get Launchpad content-gap statistics. 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": "get_launchpad_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional filters: customerId, websiteIds (comma-separated numeric IDs; mutually exclusive with websiteId/serverHost), websiteId or serverHost. Omit website selectors for all authorized websites in the customer context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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: +{
      +  "customerId": {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  "serverHost": {
      +    "maxLength": 253,
      +    "type": "string"
      +  },
      +  "websiteId": {
      +    "$ref": "#/properties/query/properties/customerId"
      +  },
      +  "websiteIds": {
      +    "maxLength": 2048,
      +    "type": "string"
      +  }
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Optional filters: websiteId or serverHost."New value: +"Optional filters: customerId, websiteIds (comma-separated numeric IDs; mutually exclusive with websiteId/serverHost), websiteId or serverHost. Omit website selectors for all authorized websites in the customer context."
  3. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: results are scoped to the linked Market Brew account's visibility. It says nothing about aggregation, time range, or result shape, so it is additive but thin.

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

Conciseness3/5

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

Two short sentences, appropriately sized and front-loaded. However, the first sentence is pure repetition of the title and earns no place, leaving only the visibility note as real content.

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

Completeness2/5

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

With no output schema, the description must convey what 'content-gap statistics' actually returns, and it does not — no metrics, dimensions, or aggregation level are mentioned. For a stats tool with zero return-value documentation, an agent cannot predict the response it will get.

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 single nested 'query' object already documents customerId, websiteIds, websiteId, and serverHost including mutual exclusivity and omit-behavior. The description adds no meaning beyond the schema, which is the expected baseline 3 when the schema does the work.

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

Purpose2/5

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

The description is a near-verbatim restatement of the tool name and title ("get Launchpad content-gap statistics"), adding no specificity about which statistics, what a 'content gap' means here, or what shape the result takes. It does not differentiate from sibling tools such as list_launchpad_keyword_gaps or list_launchpad_prompt_gaps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

It offers only a circular trigger ("when the user asks to get Launchpad content-gap statistics"), which gives no real selection criteria and names no alternatives or exclusions. An agent facing keyword-gap, prompt-gap, and general launchpad tools gets no help choosing this one over its siblings.

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