Skip to main content
Glama
Sign In
linkedin-mcp-pro

linkedin-mcp-pro

by horizonbymuneeb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_audit_log

Retrieve recent audit log entries to monitor all actions, statuses, and details. Filter by action type and set the number of entries.

Instructions

Get the most recent audit log entries (every action, with status and details).

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_audit_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoFilter by action type, e.g. 'connection'
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It reveals recency, scope, and return content, but omits ordering details, permission needs, rate limits, or pagination behavior beyond the limit parameter.

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?

Single sentence, front-loaded, and concise. Every word adds value with no redundancy.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple list tool with two optional params. Covers what it returns and its recency, but lacks detail on response structure, pagination, and broader usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 50% description coverage (action described, limit not). The description adds no extra parameter meaning beyond implying action can filter. Does not clarify limit's role or action format.

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 clearly states the tool gets the most recent audit log entries, specifying scope ('every action') and content ('with status and details'), which distinguishes it from sibling tools that retrieve different resources like posts or stats.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. Does not mention prerequisites, when not to use, or compare with siblings like get_feed or get_daily_stats.

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

Deploy Server

Other Tools