Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List campaigns a safety approval kept paused

luca_review_queue_kept_campaigns
Read-onlyIdempotent

Lists campaigns left paused by a safety review and indicates whether each is still paused or was resumed, so you can identify the enrollment to resume.

Instructions

List the campaigns that approving this safety review kept paused for the lead, and whether each one is still paused or the coach already resumed it. Use it to find the enrollment to pass to luca_campaigns_enrollments_resume. The list is empty for a review that kept nothing paused.

Luca operation: GET /api/review-queue/{id}/kept-campaigns Required scopes: review_queue:read Required OAuth scope: luca:read; data sensitivity: full_content Does not require idempotency. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

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": {
      "id": "<id>"
    },
    "name": "luca_review_queue_kept_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description goes further by disclosing required scopes (review_queue:read, luca:read), a 'full_content' data sensitivity level, and the empty-list edge case. The 'Does not require idempotency' line is largely redundant with idempotentHint=true, which keeps it just short of a 5.

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?

The two functional sentences are front-loaded and carry the real decision-relevant content; the endpoint, scope and idempotency lines are conventional metadata blocks. Nothing is verbose, though the idempotency sentence adds little beyond the annotations.

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?

Return values are covered by the output schema, safety by annotations, and the description adds auth scopes, workspace-override behavior, empty-result handling and the downstream consumer of the result. For a three-parameter read tool this is close to complete, with only the exact meaning of `id` left implicit.

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

Parameters4/5

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

With 67% schema description coverage, the two workspace parameters are already documented in the schema, but the description adds the operational meaning that they 'override the default workspace configured by environment.' The required `id` parameter is only implicitly defined via 'the campaigns that approving this safety review kept paused' and the raw endpoint path, so its semantics are inferable rather than stated.

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 and resource ('List the campaigns that approving this safety review kept paused') with the exact scope narrowed to one lead's review, plus the state each campaign is in. This is far from a tautology of the name and an agent can distinguish it from siblings like luca_review_queue_list or luca_campaigns_enrollments_list.

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?

Explicitly routes the agent: 'Use it to find the enrollment to pass to luca_campaigns_enrollments_resume', and pre-empts confusion about a null result by stating 'The list is empty for a review that kept nothing paused.' It gives clear context but no explicit when-not guidance or a competing alternative for the same lookup.

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

Deploy Server

Other Tools