Skip to main content
Glama

Analook — Competitor Intelligence

by io.github.Gingiris

get_report

Fetch the full competitor analysis report as structured JSON.

Reports contain: website snapshot, Wayback Machine history, SEO/traffic
data (DataForSEO), social media presence, Product Hunt launches, GitHub
stats, pricing, funding, AI-generated business insights, growth
playbooks, and more.

Args:
    job_id: ID from analyze_competitor(); status must be 'completed'

Returns:
    The full report dict (nested structure), or {error} if not found / not ready.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden. It discloses that the tool returns either a full nested dict or an error for missing/incomplete reports, and it explains the content scope (website snapshot, Wayback, SEO, etc.). It does not discuss auth, rate limits, or side effects, but for a read-only fetch these are less critical.

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 well-structured with a lead sentence, an Args/Returns format, and a precise list of report contents. The list of data sources is somewhat long but serves as useful context for an agent selecting the right tool. It is front-loaded and does not waste words on filler.

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 lack of output schema and annotations, this description is fairly complete: it specifies the return type, error behavior, and a prerequisite. It also enumerates the report's contents, which helps an agent judge whether the data matches the user's need. It could go deeper on the exact nesting or size, but for a typical retrieval tool it suffices.

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?

The description adds meaning to job_id beyond the schema: it explains it is the ID from analyze_competitor() and that the report must have status 'completed'. The context and conversation_id parameters are adequately described in the schema, so overall parameter semantics are well covered despite the 67% schema coverage.

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 states a specific verb ('Fetch'), a clear resource ('full competitor analysis report'), and the output format ('structured JSON'). It distinguishes itself from sibling tools like get_report_markdown (presumably text/markdown) and get_report_status (status only), and 'full' differentiates from browse_public_reports.

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

Usage Guidelines4/5

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

The description provides a clear prerequisite: job_id must come from analyze_competitor() and the status must be 'completed'. This implies the tool is for post-analysis retrieval and not for early polling. It also notes the error case ('not found / not ready'), but it does not explicitly name alternative tools for different report formats or status checks.

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

All Analook — Competitor Intelligence toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Most tools have clear distinct purposes: job submission, status polling, report retrieval, and listing are separated. Some potential confusion exists between get_report/get_report_markdown (same content, different format) and get_report_status/get_growth_audit (both return status for different job types), but descriptions clarify these boundaries.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores: analyze_competitor, browse_public_reports, get_growth_audit, get_report, get_report_markdown, get_report_status, list_my_reports, run_growth_audit. No mixed conventions or camelCase.

Tool Count5/5

8 tools is well-scoped for a competitor intelligence server, covering two distinct workflows (competitor analysis and growth audit) plus report browsing and retrieval. Each tool serves a clear purpose without feeling bloated or skeletal.

Completeness4/5

The core lifecycle is covered: submit analysis, poll status, fetch report in JSON/Markdown, list personal reports, and browse public reports. Minor gaps remain, such as no way to list past growth audits or cancel/delete jobs, but these are not critical for the primary use case.

Resources