Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

linkedin_showcase

Fetch a LinkedIn Showcase Page by ID to retrieve its name, headline, about text, industry, followers, employees, locations, website, logo, products, affiliated pages, and recent updates.

Instructions

Get Linkedin Showcase Page Info. Returns a LinkedIn showcase page by its showcase page id. The response has the name, headline, about text, industry, follower count, employees on LinkedIn, headquarters, locations, specialties, website, logo, Products section cards when present, affiliated and similar pages, and recent updates with reactions and comment counts.

Input Schema

NameRequiredDescriptionDefault
idYesLinkedIn Showcase Page ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose what the response contains (fields returned) which is genuinely useful behavioral context. However it says nothing about auth/permission requirements, whether the id is a numeric URN vs vanity slug, rate limits, or error behavior for an unknown id.

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?

Two sentences, front-loaded with the purpose and then the return payload; no filler. The second sentence is a long enumerated field list, but every item conveys what the caller can expect, so it earns its length.

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

Completeness4/5

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

There is no output schema, so the description correctly takes on the job of enumerating return fields, which it does thoroughly. For a single-parameter read tool this is nearly complete, with only auth/error context 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 description coverage is 100% for the single 'id' parameter, so the schema already defines it as the 'LinkedIn Showcase Page ID'. The description repeats that the page is fetched by its id but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ('Get Linkedin Showcase Page Info... Returns a LinkedIn showcase page by its showcase page id'), which is clearly distinguishable from the LinkedIn sibling tools (linkedin_company, linkedin_product). But it never explicitly contrasts itself with linkedin_company, so an agent must infer the difference between a Showcase Page and a Company Page.

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?

There is no guidance on when to use this tool versus alternatives like linkedin_company or linkedin_product, and no prerequisites or exclusions are given. The description only describes output, leaving selection entirely to inference from the tool name.

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