Linkup Company Research MCP

competitive_landscape

Analyze a company's competitive position by identifying competitors, market positioning, differentiators, and competitive advantages from industry reports and company materials.

Instructions

Analyze a company's competitive position in their market.

Identifies competitors, market positioning, differentiators, and competitive advantages through research of industry reports, review sites, and company materials.

Args: company_name: The name of the company to research output_format: "answer" for natural language with sources, "structured" for JSON include_images: Include competitor logos and comparison visuals max_results: Maximum sources to consider (1-50)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company_name": "<company_name>"
    },
    "name": "competitive_landscape"
  }
}

Input Schema

Name	Required	Default
`max_results`	No
`company_name`	Yes
`output_format`	No	answer
`include_images`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Jul 6, 2026

TDQS

A3.7/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. It discloses the research sources (industry reports, review sites, company materials) but does not reveal potential limitations like data freshness, scope, or time required.

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 concise with a clear structure: purpose statement, output list, and parameter list. It avoids unnecessary details but is slightly verbose in listing the output components.

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?

Given the presence of an output schema and four parameters, the description provides adequate context. It explains the tool's function and parameters, though it could elaborate on output behavior (e.g., when data is unavailable).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It lists all four parameters in the Args section with brief explanations, including possible values for output_format and range for max_results, adding meaning beyond the schema titles.

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's purpose: 'Analyze a company's competitive position in their market.' It specifies the output components (competitors, positioning, differentiators, advantages) and distinguishes from sibling tools that cover other aspects like business model or culture.

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. The description lacks explicit context for appropriate usage, such as prerequisites or conditions, and does not mention when not to use it.

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

Deploy Server