Skip to main content
Glama

Market Brew

Add Spotlight Author opportunities to Launchpad

add_spotlight_author_to_launchpad

Use this when the user explicitly asks to add Spotlight Bridge opportunities to Launchpad. Identify the destination Crew, licensed website, source analysis, and selected entities first. This persists opportunities. Repeated additions can increment detection counts. Do not retry successful entries after a partial failure.

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": {
      "body": "<body>"
    },
    "name": "add_spotlight_author_to_launchpad"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the operation persists opportunities, that repeated additions can increment detection counts, and that successful entries should not be retried after a partial failure. Those are useful mutation side effects and failure-handling details not captured by the annotations. It does not cover authorization requirements or the exact response shape, but it adds substantial behavioral context.

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?

The description is four sentences, front-loaded with the usage trigger, and every sentence carries actionable information about prerequisites, persistence, side effects, or failure handling. There is no filler.

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 complex mutation with a deeply nested single object parameter and no output schema, the description covers the trigger, prerequisite inputs, persistence side effects, and partial-failure behavior. However, it leaves most nested schema fields unexplained, so an agent would still struggle to construct a correct request body from the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It names four high-level pieces (Crew, licensed website, source analysis, selected entities), which maps to some nested fields, but the schema contains many additional nested properties such as prompts, pageSize, targetUrl, snapshotId, compressionLevel, and recommendations that are left unexplained.

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 states a specific verb and resource: add Spotlight Bridge opportunities to Launchpad. It is clear enough to distinguish a write/persist action from analysis siblings, but it does not explicitly differentiate this from add_spotlight_visualizer_to_launchpad or name the relevant source-analysis tool.

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?

It gives an explicit trigger: use when the user explicitly asks to add Spotlight Bridge opportunities to Launchpad. It also lists prerequisites such as identifying the destination Crew, licensed website, source analysis, and selected entities. It does not state when not to use it or name a specific alternative tool.

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