Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Read LinkedIn attachment

read_linkedin_attachment
Read-only

Use this to read a file someone sent or received on LinkedIn (e.g. "summarize the deck they sent me"). A document, spreadsheet, slide deck or image comes back readable: call read_attachment(attachment_id) to pull a document's slices or see the image. Any other type, such as a voice message, is saved to the library but isn't readable. Dict with attachment_id (pass to read_attachment), filename, mimeType, summary.

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": {
      "message_id": "<message_id>",
      "attachment_id": "<attachment_id>"
    },
    "name": "read_linkedin_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesThe message's `id` from search_linkedin_message_history.
on_behalf_ofNoA teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
attachment_idYesThe file's `id` from that message's `attachments`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely new behavior — the file is persisted into the user's attachment library and a handle is returned, and only certain mime types become readable. That persistence is additive (a new library entry, nothing existing is modified or destroyed), so it does not contradict the read-only hint, but it is the kind of side effect the agent should know about.

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?

Front-loaded with the core action, then usage, then return shape; every sentence carries information. The XML wrapper tags (<summary>, <returns>) add mild structural noise, but the <returns> block earns its place since no output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 supplies the return dict keys (attachment_id, filename, mimeType, summary) and the chaining call, plus the readable-vs-unreadable type boundary. For a three-parameter fetch tool, nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, with message_id and attachment_id already documented as coming from search_linkedin_message_history and the message's attachments list, and on_behalf_of fully explained. The description adds no further parameter meaning beyond naming read_attachment as the consumer of attachment_id, so the baseline 3 applies.

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 concrete verb and resource — fetch a file on a LinkedIn message, save it to the attachment library, return a handle — and distinguishes itself from the sibling read_attachment, which is only for pulling slices of an already-fetched document. Also implicitly separates from read_email_attachment/get_email_attachment by scoping to LinkedIn messages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger scenario ("summarize the deck they sent me"), names the required follow-up call read_attachment(attachment_id), and sets an exclusion: non-document types such as voice messages are saved but not readable. The agent knows when to call it and what to do next.

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

All Sliq 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