Skip to main content
Glama
DerrickAppOrg

Derrick App

Official

Enrich Company with LinkedIn Data

derrick_enrich_companies
Read-only

Enrich company data with 15+ LinkedIn attributes, including description, industry, size, and location, using a LinkedIn company URL.

Instructions

Enrich Company with LinkedIn Data Enrich companies with +15 attributes from a LinkedIn company URL Cost: 1 credit(s) per call. Category: enrich::linkedin::company

Adds +15 LinkedIn attributes (name, description, industry, size, location, website, followers, specialties, etc.). Requires a full LinkedIn URL — if you only have the name, use search_companies first (+1 credit). Requires the Derrick Chrome extension.

Args: queryValue: LinkedIn company URL column

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryValueYesLinkedIn company URL column
Behavior5/5

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

Discloses credit cost, extension requirement, and enrichment behavior. Consistent with readOnlyHint and openWorldHint annotations, adding useful context beyond annotations.

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?

Concise, front-loaded with title and summary, followed by requirements and args. Every sentence adds value.

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

Completeness5/5

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

Covers purpose, prerequisites, alternatives, cost, and category. Complete for a single-parameter enrichment tool with no output schema.

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 coverage is 100% for the single parameter, and the description repeats the schema description without adding further meaning. Baseline 3 is appropriate.

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 enriches companies with +15 LinkedIn attributes using a LinkedIn URL. It distinguishes itself from sibling tools like derrick_enrich_profile and derrick_search_companies.

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

Usage Guidelines5/5

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

Explicitly guides when to use: requires full LinkedIn URL; if only name, use search_companies first. Also notes the Derrick Chrome extension requirement and credit cost.

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/DerrickAppOrg/derrick-mcp'

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