Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

List Golden Lists

list_golden_lists
Read-onlyIdempotent

Retrieve the prospect or ICP Golden Lists you own or that were explicitly shared with you, including campaign IDs, without unrelated accounts. Read-only access.

Instructions

The main Golden Lists (prospect or ICP lists) the user owns or that were explicitly shared with them, with their campaign ids. Lists of unrelated accounts are not included. Reads only.

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

Input Schema

NameRequiredDescriptionDefault
config_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already cover read-only, idempotent, and non-destructive behavior, so 'Lists of unrelated accounts are not included' is the one genuinely additive disclosure, telling the agent results are filtered by ownership/sharing. 'Reads only' merely restates readOnlyHint=true. The description says results carry campaign ids, which helps, but says nothing about ordering, volume, or empty-set behavior.

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?

Three short sentences, scope stated first and the exclusion last; nothing is padded. The only waste is 'Reads only', which duplicates the annotation and could be spent on config_id instead.

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 simple zero-required-parameter list tool with no output schema, the description is mostly adequate: it discloses scope, filtering, and that campaign ids come back. It is incomplete on the one parameter it accepts and on the shape/size of the returned collection, which matters since there is no output schema to fall back on.

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?

The single parameter config_id has 0% schema description coverage, and the description never mentions it, so the agent has no idea whether it filters, scopes, or overrides the list. With low coverage the description is expected to compensate, and it does not.

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 names a specific resource (Golden Lists, glossed as prospect or ICP lists) and a specific verb (list), and it scopes ownership ('the user owns or that were explicitly shared with them'). It does not name the sibling that returns a single list (read_golden_list), but the collection-vs-detail distinction is clear from the description itself.

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?

Usage is implied rather than stated: an agent can infer this is the discovery step before reading a specific list. There is no explicit when-to-use, no mention of read_golden_list or get_prospect_list as follow-on alternatives, and no guidance on whether pagination or empty results require another call.

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