Skip to main content
Glama
competlab

competlab-mcp-server

get_tech_trust_history

Get paginated history of Tech & Trust monitoring runs with completion timestamps. Compare changes over time, each run captures a full snapshot of all competitors. Use runId to retrieve run details.

Instructions

Get paginated history of Tech & Trust monitoring runs with completion timestamps. Use this to compare changes over time — each run captures a full snapshot of all competitors. Retrieve specific run data with get_tech_trust_run_detail using the runId from this response. Read-only. Returns paginated JSON array with pagination.hasMore flag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID (from list_projects)
pageNoPage number (1-indexed, default: 1)
limitNoItems per page (default: 20, max: 100)

Implementation Reference

  • src/tools.ts:93-113 (registration)
    The tool 'get_tech_trust_history' is registered as a ToolDef entry in the tools array with its name, description, Zod schema parameters, and API path mapping.
    // ── Tech & Trust ──────────────────────────────────────────
    {
      name: "get_tech_trust_dashboard",
      description:
        "Get the latest Tech & Trust Profile for all competitors. Returns security headers (grade A-F, HSTS, CSP, X-Frame-Options), trust signals (compliance, reviews, social proof, certifications — 24 signals in 4 categories), technology stack (47 tech, 43 growth, 27 engagement tools), robots.txt AI bot blocking status, DNS infrastructure, and AI analysis with insights and actions. Use this for the current snapshot; use get_tech_trust_history for past runs. Read-only. Returns JSON object.",
      parameters: z.object({
        projectId: objectId("Project ID (from list_projects)"),
      }),
      path: (a) => `/v1/projects/${a.projectId}/tech-trust`,
    },
    {
      name: "get_tech_trust_history",
      description:
        "Get paginated history of Tech & Trust monitoring runs with completion timestamps. Use this to compare changes over time — each run captures a full snapshot of all competitors. Retrieve specific run data with get_tech_trust_run_detail using the runId from this response. Read-only. Returns paginated JSON array with pagination.hasMore flag.",
      parameters: z.object({
        projectId: objectId("Project ID (from list_projects)"),
        ...pagination,
      }),
      path: (a) => `/v1/projects/${a.projectId}/tech-trust/history`,
      queryParams: ["page", "limit"],
    },
  • Input schema for get_tech_trust_history: requires projectId (24-char hex string) and optional pagination params (page, limit).
    parameters: z.object({
      projectId: objectId("Project ID (from list_projects)"),
      ...pagination,
    }),
  • Generic handler that executes all tools (including get_tech_trust_history) by calling the API via apiGet with the path and query params defined in the ToolDef.
    for (const tool of tools) {
      server.tool(tool.name, tool.description, tool.parameters.shape, async (args: Record<string, any>) => {
        const path = tool.path(args);
        const query: Record<string, any> = {};
        for (const key of tool.queryParams ?? []) {
          if (args[key] !== undefined) query[key] = args[key];
        }
        return apiGet(path, Object.keys(query).length ? query : undefined);
      });
    }
  • The apiGet helper that performs the actual HTTP GET request to the CompetLab API, using the COMPETLAB_API_KEY env var for authentication.
    const API_BASE = "https://api.competlab.com";
    
    export async function apiGet(
      path: string,
      query?: Record<string, string | number>,
    ): Promise<{ content: Array<{ type: "text"; text: string }>; isError?: true }> {
      const apiKey = process.env.COMPETLAB_API_KEY;
      if (!apiKey) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                error: "api_key_missing",
                message: "COMPETLAB_API_KEY environment variable is not set",
              }),
            },
          ],
          isError: true,
        };
      }
    
      const url = new URL(`${API_BASE}${path}`);
      if (query) {
        for (const [k, v] of Object.entries(query)) {
          if (v !== undefined) url.searchParams.set(k, String(v));
        }
      }
    
      try {
        const res = await fetch(url, {
          headers: { "CL-API-Key": apiKey },
        });
    
        const body = await res.text();
    
        if (!res.ok) {
          return { content: [{ type: "text", text: body }], isError: true };
        }
    
        return { content: [{ type: "text", text: body }] };
      } catch (err) {
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify({
                error: "api_unreachable",
                message:
                  err instanceof Error ? err.message : "Failed to reach CompetLab API",
                status: 503,
              }),
            },
          ],
          isError: true,
        };
      }
    }
  • src/index.ts:16-25 (registration)
    The generic registration loop that iterates over all ToolDef entries (including get_tech_trust_history) and registers them with the MCP server via server.tool().
    for (const tool of tools) {
      server.tool(tool.name, tool.description, tool.parameters.shape, async (args: Record<string, any>) => {
        const path = tool.path(args);
        const query: Record<string, any> = {};
        for (const key of tool.queryParams ?? []) {
          if (args[key] !== undefined) query[key] = args[key];
        }
        return apiGet(path, Object.keys(query).length ? query : undefined);
      });
    }
Behavior4/5

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

Despite no annotations, the description states the tool is read-only and describes the return format: paginated JSON array with pagination.hasMore flag. This adds useful behavioral context, though it could mention additional details like ordering or rate limits.

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?

The description is compact (3 sentences) with purpose front-loaded. Every sentence adds value: purpose, usage context, read-only flag, and return format hints. No unnecessary words.

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?

Without an output schema, the description explains the pagination flag and references runId for detail retrieval. It covers the core aspects, but could elaborate more on the array fields or default ordering. Nonetheless, it is sufficient for an agent to use effectively.

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?

The input schema covers all 3 parameters with descriptions, and the description does not add extra meaning beyond the schema. However, it provides useful context that the response contains runId for use with a sibling tool, which marginally helps understanding.

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 retrieves a paginated history of Tech & Trust monitoring runs with completion timestamps. It uses a specific verb-resource combination and distinguishes itself from sibling 'get_tech_trust_run_detail' by indicating that this history provides runIds for further detail retrieval.

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?

The description explicitly tells when to use this tool: 'Use this to compare changes over time — each run captures a full snapshot of all competitors.' It also provides an alternative: 'Retrieve specific run data with get_tech_trust_run_detail using the runId from this response,' giving clear context for decision-making.

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/competlab/competlab-mcp-server'

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