Skip to main content
Glama
G-Hensley
by G-Hensley

Update LinkedIn Metrics

update_linkedin_metrics

Update follower count, connections, profile views, post impressions, and engagement rate for your LinkedIn accounts.

Instructions

Update LinkedIn metrics for an account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountYesWhich account to update
followersNoUpdate follower count
connectionsNoUpdate connection count (personal only)
profile_viewsNoUpdate profile views (last 90 days)
post_impressionsNoUpdate post impressions
engagement_rateNoUpdate engagement rate (as percentage)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
Behavior2/5

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

No annotations are present, so the description must fully disclose behavior. It only states 'Update', implying mutation, but does not mention side effects, overwrite behavior, permissions, or confirmation. The brevity fails to inform the agent of important behavioral traits.

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?

The description is extremely concise at six words, but it sacrifices completeness. While it earns points for being short, it lacks detail. A 4 reflects good conciseness but not optimal due to under-specification.

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?

Given the tool has 6 parameters and an output schema, the description does not explain the result of the operation or how the parameters interact. It misses context about return values and operational effects, making it only minimally adequate.

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?

The input schema has 100% description coverage, so each parameter's meaning is clearly documented in the schema. The description adds no additional semantic beyond the schema, meeting the baseline for high coverage.

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 description 'Update LinkedIn metrics for an account' clearly identifies the verb (update) and resource (LinkedIn metrics), distinguishing it from sibling tools like 'get_linkedin_metrics' (retrieve) and 'update_linkedin_profile' (profile data). However, it is somewhat tautological and could be more specific.

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 is provided on when to use this tool versus alternatives, prerequisites, or exclusions. The description lacks any contextual usage advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/G-Hensley/myself-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server