Skip to main content
Glama

Update opportunity status

opportunities.update

Set an opportunity’s status to found, approved, shipped, or snoozed to track SEO and AEO fixes; snoozing defaults to 7 days.

Instructions

Pro: set opportunity status to found|approved|shipped|snoozed (snooze defaults to 7 days). Requires QUALITYKIT_API_KEY + QUALITYKIT_API_BASE.

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": {
      "opportunityId": "<opportunityId>",
      "status": "<status>"
    },
    "name": "opportunities.update"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNo
statusYes
apiBaseUrlNo
snoozedUntilNo
opportunityIdYesStable opportunity id (grow or GSC id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose two useful facts: snooze defaults to 7 days, and the operation requires QUALITYKIT_API_KEY plus QUALITYKIT_API_BASE. However, it doesn't say whether a status change is reversible, what happens to snoozedUntil when status isn't 'snoozed', or what the call returns on success.

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

Conciseness4/5

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

Two compact sentences with the status list and the credential requirement front-loaded; nearly every clause carries information. The 'Pro:' prefix is slightly cryptic but doesn't obscure the content.

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 five-parameter mutation tool with no annotations and no output schema, the description covers the core action, the status vocabulary, one default, and auth. It leaves gaps around the roles of apiKey/apiBaseUrl relative to the env vars and around return behavior, which matter for correct invocation.

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 20%, so the description should compensate but mostly doesn't: opportunityId, apiKey, apiBaseUrl, and snoozedUntil are unexplained. It does add real meaning for one parameter by giving the snooze default of 7 days, which the enum alone does not convey.

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?

States a specific verb and resource ('set opportunity status') and enumerates the four allowed target states, so the agent knows exactly what the call changes. It doesn't differentiate from the other opportunity siblings (list/sync), but the verb 'set ... status' is self-distinguishing.

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?

There is no indication of when to use this versus opportunities.sync or opportunities.list, nor any prerequisite or precondition beyond the credential note. The only implied guidance is that this is a status-transition tool.

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