Skip to main content
Glama

List marketing opportunities

list_growth_opportunities
Read-onlyIdempotent

Places the business could get listed or be seen — directories, communities, media/PR and partnership leads — with priority, why each fits, a suggested approach and the owner's progress (suggested, bookmarked, in_progress, submitted, verified, skipped). Filter by channel or status. These are suggestions; the owner does the submitting.

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": {
      "site_id": "<site_id>"
    },
    "name": "list_growth_opportunities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many (default 50)
statusNo
channelNo
site_idYesThe site, from list_sites
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
      +  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the six-state progress lifecycle per item and the explicit note that the tool only surfaces suggestions while the owner performs the submission — clarifying that no state change happens here.

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, front-loaded with what an opportunity is and what each record contains, then filters, then the read-only caveat. The parenthetical status list is the only dense element and it earns its place by previewing the filter domain.

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?

With no output schema, the description carries the burden of describing returned records, and it does so well (priority, fit rationale, suggested approach, owner progress). The only gaps are pagination/limit behavior and the purpose of the user_goal parameter, both partially covered by the input schema.

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 coverage is 60% and the two enum parameters (channel, status) are fully documented in the schema, including the enum values that the description merely restates. The description adds no semantics for limit, site_id, or user_goal, so it does not compensate for the uncovered parameters — baseline 3 applies.

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

Purpose5/5

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

States a specific verb-plus-resource (lists placement/visibility opportunities) and enumerates the concrete categories — directories, communities, media/PR, partnership leads — which cleanly separates it from siblings like list_growth_content_ideas or list_marketing_ideas. It also names the per-item payload (priority, fit rationale, suggested approach, owner progress), so an agent knows exactly what it gets back.

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?

It says 'Filter by channel or status', which implies the two supported narrowing modes, but gives no explicit when-to-use guidance relative to get_growth_dashboard, list_growth_content_ideas, or update_growth_opportunity. The closing line 'These are suggestions; the owner does the submitting' usefully signals this tool does not act, but that is the only exclusion stated.

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