LinkDrop

List contact lists

lnkdrp_list_contact_lists

Read-onlyIdempotent

The workspace's contact lists this person can see with their names, descriptions, member counts, visibility and owner: team lists and their own private ones; other people's private lists are not listed. visibility filters: team, private (their own private ones), or mine (every list they own). createdBy says who made it: name, via (web, api or mcp) and the agent when known; "Former member" for someone no longer in the workspace. Each list has labels (the workspace's tags on it, lnkdrp_tag with listId) and projects (the projects it is filed under). projectId keeps the lists filed under that project; labels keeps those carrying any of the named tags. lnkdrp_get_contact_list returns a list's members. query searches the name and, with a word of three or more letters, the description, the members (name or address), workspace tags and projects; rows then come best match first and each carries match { in, snippet, name }: in is name, description, member, label or project; name is the member, tag or project that matched (a member's name or address is their own words). totalCapped true means more than 500 matched and total is a lower bound. searchIn: name searches the name only. contactId keeps the lists holding that contact. order: relevance (the default with a query), name (the default otherwise), updated or newest. Dates: a bare date (2026-10-28) is that whole day in the workspace's time zone (UTC when it has none) and a To date includes that day; a time with Z or an offset is that exact instant; the answer's dateRange gives the time zone and the exact instants used. Page-based: total says how many there are.

Input Schema

Name	Required	Description
`page`	No	1-based page number.
`limit`	No	Lists per page (1-100).
`order`	No	relevance: best match (the default with a query). name: A-Z (the default otherwise). updated: changed most recently. newest: created most recently.
`query`	No	Searches the list's name, description, members' names and addresses, workspace tags and projects, case-insensitively.
`labels`	No	Only contact lists carrying any of these workspace tags (lnkdrp_tag), by name or slug (1-20).
`searchIn`	No	all (default): everything query searches. name: the list's name only.
`contactId`	No	Only the lists holding this contact (24 hex chars), from lnkdrp_list_contacts.
`createdTo`	No	Only contact lists created on or before this date (that whole day) or time.
`projectId`	No	Only contact lists filed under this project (24 hex chars).
`updatedTo`	No	Only contact lists last changed on or before this date (that whole day) or time.
`visibility`	No	all (default): every list this person can see. mine: every list they own. team: shared lists. private: their own private lists.
`createdFrom`	No	Only contact lists created on or after this date (2026-10-28) or time.
`updatedFrom`	No	Only contact lists last changed on or after this date (2026-10-28) or time.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 29, 2026

addedInput schema / properties / contactId

Added value: +{
+  "description": "Only the lists holding this contact (24 hex chars), from lnkdrp_list_contacts.",
+  "pattern": "^[a-fA-F0-9]{24}$",
+  "type": "string"
+}

addedInput schema / properties / createdFrom

Added value: +{
+  "description": "Only contact lists created on or after this date (2026-10-28) or time.",
+  "maxLength": 40,
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}",
+  "type": "string"
+}

addedInput schema / properties / createdTo

Added value: +{
+  "description": "Only contact lists created on or before this date (that whole day) or time.",
+  "maxLength": 40,
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}",
+  "type": "string"
+}

addedInput schema / properties / order

Added value: +{
+  "description": "relevance: best match (the default with a query). name: A-Z (the default otherwise). updated: changed most recently. newest: created most recently.",
+  "enum": [
+    "relevance",
+    "name",
+    "updated",
+    "newest"
+  ],
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Searches the list's name, description, members' names and addresses, workspace tags and projects, case-insensitively.",
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / searchIn

Added value: +{
+  "description": "all (default): everything query searches. name: the list's name only.",
+  "enum": [
+    "all",
+    "name"
+  ],
+  "type": "string"
+}

addedInput schema / properties / updatedFrom

Added value: +{
+  "description": "Only contact lists last changed on or after this date (2026-10-28) or time.",
+  "maxLength": 40,
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}",
+  "type": "string"
+}

addedInput schema / properties / updatedTo

Added value: +{
+  "description": "Only contact lists last changed on or before this date (that whole day) or time.",
+  "maxLength": 40,
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}",
+  "type": "string"
+}

Changed3 schema fields changedOct 28, 2026

addedInput schema / properties / labels

Added value: +{
+  "description": "Only contact lists carrying any of these workspace tags (lnkdrp_tag), by name or slug (1-20).",
+  "items": {
+    "maxLength": 60,
+    "minLength": 1,
+    "pattern": "^[^,]*$",
+    "type": "string"
+  },
+  "maxItems": 20,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / projectId

Added value: +{
+  "description": "Only contact lists filed under this project (24 hex chars).",
+  "pattern": "^[a-fA-F0-9]{24}$",
+  "type": "string"
+}

addedInput schema / properties / visibility

Added value: +{
+  "description": "all (default): every list this person can see. mine: every list they own. team: shared lists. private: their own private lists.",
+  "enum": [
+    "all",
+    "mine",
+    "team",
+    "private"
+  ],
+  "type": "string"
+}

AddedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds non-obvious traits: other people's private lists are excluded, `totalCapped` means more than 500 matched and `total` is a lower bound, and date handling specifies timezone and inclusive `To` behavior. These disclosures materially help an agent interpret results correctly, though the wall-of-text format makes them harder to absorb than they should be.

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

Conciseness3/5

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

The core purpose is front-loaded, but the description is a single dense paragraph that repeats schema content (order defaults, visibility filter definitions, date parsing) and packs many clauses into semicolon-separated run-ons. It is information-rich but not efficiently structured for quick agent parsing.

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 13 parameters and no output schema, the description does a solid job covering return content (names, descriptions, member counts, visibility, owner, labels, projects, match details, `total`, `dateRange`) and pagination. It could be clearer about the full non-search response shape, but it provides enough for correct invocation and interpretation.

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, but the description adds meaning beyond the schema: it explains that `visibility=mine` means every list the person owns, that `query` searches the description only for words of three or more letters, and that `match` rows carry `{ in, snippet, name }`. These details are useful and not fully captured in the schema descriptions.

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?

The description opens with a specific verb and resource ("The workspace's contact lists this person can see") and immediately scopes it by visibility and privacy. It also distinguishes itself from the sibling `lnkdrp_get_contact_list`, which "returns a list's members," so an agent can tell the two apart without opening a 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?

It explains what each filter does (`visibility`, `query`, `labels`, `projectId`, `contactId`, `searchIn`) and points to `lnkdrp_get_contact_list` for member-level details, giving clear usage context. It stops short of explicitly saying when not to use this tool or naming a more specific alternative for listing scenarios, so it is strong but not exhaustive.

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

All LinkDrop tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?