Audit LinkedIn profile completeness and section strength to identify areas for improvement and receive actionable recommendations for optimizing discoverability.
Audit your profile completeness, section strength, and generate actionable recommendations to optimize LinkedIn discoverability.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys an audit/advice behavior and is non-mutating in tone, but it does not explicitly state that it only reads data, whether it uses cached or live profile data, or whether it modifies anything. Given the simple analysis nature, this is a moderate gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that directly states what the tool does and the value it produces. No filler or repeated schema information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless tool with an output schema, the description is largely adequate: it identifies the subject ('your profile'), the action, and the output (recommendations). It would be slightly stronger with an explicit 'does not modify your profile' or a note about when to use it, but nothing required for invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has zero parameters, and the input schema already carries complete coverage (100%). The description adds no parameter detail, but none is needed; baseline 4 applies for a parameterless tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific action ('Audit') on a clear resource ('your profile') and specifies the deliverable ('actionable recommendations'). It is readily distinguishable from sibling tools like get_my_profile or update_* because it focuses on analysis and optimization advice rather than retrieval or mutation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to prefer this tool over related profile tools such as get_my_profile or update_my_headline. The description implies it is for profile optimization, but it never states when to use it versus alternatives or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.