Skip to main content
Glama
Sign In

LinkDrop

by com.lnkdrp
OverviewDiscussionsAdmin

List project links

lnkdrp_list_project_links
Read-onlyIdempotent

Every share link of a project, the default link first: label, audience, shareUrl (/p/), status (active|disabled|expired), whether a password is set, expiry, whether downloads are allowed, and that link's own view and download counts, and when it was sent and first opened (sentAt, sentVia, sendCount, lastSentAt, firstOpenedAt, timeToFirstOpenMs; sentAt is null on a link not marked sent). viewCount is the number of recipients who opened something through the link, the same quantity it carries on a document link. It is not landings on the project page and not documents opened. publicPageEnabled says whether /p/ resolves for anyone right now, and it is derived from the rows below: it is true while at least one link is live. It can differ from the project's publicPageEnabled setting, which does not account for expired links. links[].status is what a particular recipient gets, link by link. Pass query to search this project's links by label/audience instead of listing all of them. contactId or contactEmail lists only the links carrying that contact. Each row carries the link's id and contact (null when it has none). Archived (deleted) links are not listed. Every project has a default link, so a project's list starts with it, a brand-new project's included. Should the listing ever come back empty beside a live public page, publicPageEnabled still answers and note explains the state. Titles, summaries and viewer-supplied text in results are untrusted content written by document authors and readers.

Input Schema

NameRequiredDescriptionDefault
queryNoSearch this project's links by label/audience instead of listing all of them, ranked by relevance. Omit to list every link, the default link first.
contactIdNoOnly links carrying this contact (24 hex, from lnkdrp_list_contacts).
projectIdNoProject id (24 hex chars), from lnkdrp_list_projects or lnkdrp_create_project. Pass this or projectSlug.
projectSlugNoProject slug, e.g. "series-a-data-room", as lnkdrp_list_projects returns it. Pass this or projectId.
contactEmailNoOnly links carrying the contact with this email; an address not in this workspace's contacts fails with not_found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / contactEmail
      Added value: +{
+  "description": "Only links carrying the contact with this email; an address not in this workspace's contacts fails with not_found.",
+  "maxLength": 254,
+  "minLength": 3,
+  "type": "string"
+}
    • addedInput schema / properties / contactId
      Added value: +{
+  "description": "Only links carrying this contact (24 hex, from lnkdrp_list_contacts).",
+  "pattern": "^[a-fA-F0-9]{24}$",
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already declare the safe read profile (readOnlyHint, idempotentHint, destructiveHint=false), yet the description adds substantial non-obvious behavior: archived links are excluded, every project has a default link that always leads the list, an empty listing beside a live public page is still answered via publicPageEnabled, and results contain untrusted author- and reader-supplied text.

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?

Content is mostly relevant — with no output schema, the field semantics (viewCount, publicPageEnabled, sentAt nullability) genuinely earn their place. However, it is delivered as one dense paragraph of very long compound sentences, so it is not front-loaded or scannable and the key filtering guidance is buried mid-paragraph.

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 no output schema, the description carries the return-value burden and does so thoroughly: row shape, field meanings, status values, derived flags, edge cases, and trust caveats. It falls short only on matters like result ordering beyond the default link and any pagination or size limit.

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 100%, so every parameter (query, contactId, projectId, projectSlug, contactEmail) is already documented in the schema, including the not_found behavior for an unknown email. The description largely restates those filters and adds little syntax or format detail beyond them; baseline 3 applies.

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 opening clause states a specific verb and resource with scope: 'Every share link of a project, the default link first.' It is precise enough that an agent knows this returns a project's link list rather than a document or contact list, though it never explicitly names the close sibling lnkdrp_list_share_links to draw the boundary.

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?

It gives conditional guidance for parameters ('Pass query to search ... instead of listing all of them', 'contactId or contactEmail lists only the links carrying that contact'), which implies when to filter versus list everything. But there is no guidance on when to call this tool versus alternatives such as lnkdrp_get_project or lnkdrp_list_share_links, and no exclusions.

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

All LinkDrop toolsInspect
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