Skip to main content
Glama

List a list's rows

get_list_rows
Read-only

Use this when the user wants to see who or what is on a list. Returns one page of its rows, people in a people list and companies in a company list, with job, company, and the email addresses and phone numbers already saved. Narrow the rows with filters, order them with sortBy, and for the next page send the page's next cursor with the same filters and sort. Free. It reads what is saved: it does not look up missing email addresses or phone numbers.

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": {
      "listId": "<listId>"
    },
    "name": "get_list_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoThe `pagination.nextCursor` of the page before. Later pages keep the first page's size.
detailNoHow much of each row to return. `short` (the default) leaves out the long fields; `full` returns every field, so ask for few rows with it.short
listIdYesThe list's id.
sortByNoThe field to sort by. People lists: `firstName`, `lastName`, `jobTitle`, `createdAt`, `address.city`, `address.country`, a company field such as `company.name` or `company.linkedInHeadCount`, or `customColumns_<columnId>`. Company lists: `name`, `domain`, `industry`, `revenue`, `linkedInHeadCount` or `customColumns_<columnId>`. A field it does not know keeps the list's own order.
filtersNoOnly the rows that match: a JSON object written as a string, at most 8,000 characters. A row must match every key, and any of a key's values. Text keys take an array of values or {"include": [...], "exclude": [...]}: name, title, dept, level, industryName, country, state, personalLocation, companyName, companyIndustry, companyHeadQuartersCountry, companyLocation, website, campaignEngagement and otherLists (names of other lists). numberOfEmployees takes ranges as strings, such as "51-200" or "10001+". keywords (a job title, with * and ? as wildcards) and linkedinUrl take one string. enrichedEmail (enriched, not_enriched, no_emails_found), enrichedPhone (enriched, not_enriched) and emailValidity (valid, invalid, catch-all, unknown, do_not_mail, personal, unverified) take {"include": [...]} or {"exclude": [...]}. icpMatch takes ["yes"] or ["no"]. Company lists take companyName, companyIndustry, companyHeadQuartersCountry, website, numberOfEmployees and campaignEngagement.
pageSizeNoRows per page.
sortOrderNoThe order `sortBy` sorts in.asc

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, closed-world, so the description isn't carrying the safety burden. It still adds non-derivable facts: the call is free, results are paginated, and only previously saved contact data is returned rather than freshly looked-up values. It doesn't discuss rate limits or exactly what the response envelope looks like beyond a page of rows.

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?

Front-loads the trigger, then the return, then the narrowing/paging mechanics, then the read-only caveat. Every sentence carries information — no restatement of the title or filler.

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 7 parameters, 2 enums, and no output schema, the description gives enough to call correctly: what a page contains, how to narrow and order it, and how to page. The remaining gap is that envelope details (such as the next cursor location) only appear indirectly through the cursor parameter description rather than in the tool description itself.

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?

Schema coverage is 100%, so the baseline is 3; the description goes beyond the schema by tying filters and sortBy to the cursor — later pages must reuse the first page's filters and sort. That is a real invocation rule not stated in any single parameter description, though the individual filter keys and sort fields are left entirely to the schema.

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 ('Returns one page of its rows') and scopes it correctly: people in a people list, companies in a company list, with the fields each row carries. It also delineates itself from enrichment behavior via 'it reads what is saved: it does not look up missing email addresses or phone numbers', so an agent can tell what class of tool this is without opening the schema.

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?

Opens with an explicit when-to-use trigger ('when the user wants to see who or what is on a list') and includes a clear when-not ('does not look up missing email addresses or phone numbers'). Pagination instructions — send the next cursor with the same filters and sort — are practical usage guidance. It stops short of naming the alternative tool an agent should call for enrichment, keeping it at 4 rather than 5.

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