Get Company Posts
get_api_v1_companies_company_postsGet company Posts By ID Group: Companies. Billing per call: 1 Credits.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | company ID | |
| start | No |
linkdapi-the-best-linkedin-professional-data-api
by com.jojapi
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden of behavioral disclosure. It does note the per-call cost and implies a read operation, but does not disclose return shape, pagination, or potential errors/limits.
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 compact and gets to the point, with a short sentence followed by two terse metadata labels. There is no filler. Slight grammatical issues like 'Posts By ID' do not severely hurt clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has only two parameters and no output schema, but the description is still too sparse. It does not explain what the response contains, how 'start' is used, or whether 'id' is effectively required, which could cause invocation errors.
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?
The description adds no parameter semantics. The schema gives the 'id' field a description ('company ID') but leaves 'start' with only an example of '0'. The description does not compensate for this gap, leaving the meaning of 'start' unclear.
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 action and resource: 'Get company Posts By ID', which aligns with the tool name and distinguishes it from company info or employee tools. However, it does not explicitly disambiguate from the more general post tools like get_api_v1_posts_all or get_api_v1_posts_info.
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 usage guidance is provided. The description only includes 'Group: Companies' and billing information, with no mention of when to use this tool versus alternatives or any prerequisites such as requiring a company ID.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.