Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List campaign comment events

luca_campaigns_comment_events_list
Read-onlyIdempotent

List matched, suppressed, blocked, and replayed comment automation events.

Instructions

List matched, suppressed, blocked, and replayed comment automation events.

Luca operation: GET /api/campaigns/comment-events Required scopes: campaigns: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

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": "luca_campaigns_comment_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
maxPagesNoMax pages the server auto-fetches and merges (default 10, hard cap 50). If more remain, the result is marked truncated with a nextCursor to continue.
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.

Output Schema

NameRequiredDescriptionDefault
resultYes
provenanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • removedOutput schema / properties / result / properties / analytics / properties / pendingReview
      Removed value: -{
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • removedOutput schema / properties / result / properties / analytics / properties / reviewRate
      Removed value: -{
-  "type": "number"
-}
  2. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint, but the description adds genuinely useful context beyond them: required scopes (campaigns:read, luca:read) and data sensitivity (full_content), which tells the agent it will be handling sensitive content. The 'Does not require idempotency' note is consistent with, not contradictory to, idempotentHint=true.

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 purpose is front-loaded in one sentence, followed by compact labeled metadata bullets. No filler, though the operation/scope lines are more boilerplate than tool-specific guidance.

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?

Output schema and annotations cover return shape and safety, and auth/sensitivity are disclosed. The notable gap is the entirely undescribed nested `query` filter object, which is the core lever for this listing tool; an agent is left to infer filter semantics from bare property names.

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 75% and maxPages/workspace params are documented in-schema, so the baseline is 3. The description only explains the workspace override and says nothing about the nine nested query filters (status, tokenState, repairState, providerHealth, etc.), which is where an agent would most need semantic guidance.

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 first line states a specific verb (List) and resource (comment automation events) with the four event categories named. It is clearly distinguishable from siblings like luca_campaigns_list or luca_campaigns_enrollments_list, though it never explicitly contrasts itself with the adjacent comment-simulation tool.

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?

The workspace override sentence gives concrete guidance for workspaceId/workspaceSlug, and 'Does not require idempotency' sets a calling expectation. However, there is no guidance on when to reach for this tool versus luca_campaigns_simulations_get or luca_campaigns_comment_simulation_suite_run, and no stated prerequisites beyond the scope line.

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