Skip to main content
Glama

Iridium: LinkedIn MCP Server

get_user_profile

Get User Profile

The user's Iridium account state: their saved targeting and voice settings, daily limits and how much of each is used today, counts of pending drafts and queued sends, unread replies, and whether LinkedIn is connected. Read-only.

Check this before any bulk action to see what capacity is left, and before asking the user to supply a setting — it may already be set. The setting fields are named exactly as update_settings takes them, so anything read here can be written straight back.

daily_dm_cap and dms_sent_today count every direct message today, new chats and replies into existing ones alike. Past the cap a new send is refused (429) and a queued one waits until the next day.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares 'Read-only', explains that daily_dm_cap and dms_sent_today count both new chats and replies, and warns that exceeding the cap yields a 429 while queued sends wait until the next day. It omits whether limits reset on a timezone boundary, which keeps it short of a 5.

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?

Content is front-loaded: what it returns, then when to call it, then the cap semantics. The trailing '### Responses: 200 Successful Response' block is boilerplate noise that adds nothing, which holds it below a 5.

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?

For a parameterless read tool with no output schema and no annotations, the description fully covers what is returned and the key behavioral caveat (the 429 cap). Nothing an agent needs in order to call it correctly or interpret the result is missing.

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?

The tool takes zero parameters, so the baseline is 4; the description adds value by stating that setting field names match update_settings exactly, meaning anything read can be written straight back. That is useful semantics beyond the empty 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?

The description names a specific resource (the user's Iridium account state) and enumerates exactly what is returned: targeting and voice settings, daily limits and usage, pending draft and queued-send counts, unread replies, and LinkedIn connection status. That enumeration distinguishes it cleanly from siblings such as get_linkedin_profile and update_settings.

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?

It gives explicit when-to-use guidance — 'Check this before any bulk action to see what capacity is left, and before asking the user to supply a setting' — and ties itself to update_settings by noting the setting fields mirror that tool's naming, so the agent knows this read feeds a specific write.

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