Skip to main content
Glama
123Ergo

unphurl-mcp

check_history

Retrieve recent URL check history with scores, phishing status, and credit usage. Paginated results show checks from the past 90 days.

Instructions

View recent URL check history. Shows what URLs have been checked, their scores, phishing status, and whether each check was free or used a pipeline credit.

Results are paginated. Use page and limit parameters to navigate. Default is 20 results per page, maximum 100.

History is retained for 90 days. Account-level stats (total credits, balance) never expire.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
limitNoResults per page, max 100 (default 20)

Implementation Reference

  • The handler function that executes the check_history tool logic. It calls api.history(page, limit) and returns the result, with error handling for auth, API errors, and unknown errors.
    async ({ page, limit }) => {
      if (!api.hasApiKey) return authError();
    
      try {
        const result = await api.history(page, limit);
        return successResult(result);
      } catch (err) {
        if (err instanceof ApiRequestError) return apiErrorToResult(err);
        return errorResult(err instanceof Error ? err.message : "Unknown error");
      }
    }
  • Input schema for check_history tool: optional page (int >= 1) and limit (int 1-100, default 20) parameters with descriptions.
        {
          description: `View recent URL check history. Shows what URLs have been checked, their scores, phishing status, and whether each check was free or used a pipeline credit.
    
    Results are paginated. Use page and limit parameters to navigate. Default is 20 results per page, maximum 100.
    
    History is retained for 90 days. Account-level stats (total credits, balance) never expire.`,
          inputSchema: {
            page: z.number().int().min(1).optional().describe("Page number (default 1)"),
            limit: z
              .number()
              .int()
              .min(1)
              .max(100)
              .optional()
              .describe("Results per page, max 100 (default 20)"),
          },
  • The registerHistoryTool function that registers 'check_history' on the MCP server via server.registerTool().
    export function registerHistoryTool(
      server: McpServer,
      api: UnphurlAPI
    ): void {
      server.registerTool(
        "check_history",
        {
          description: `View recent URL check history. Shows what URLs have been checked, their scores, phishing status, and whether each check was free or used a pipeline credit.
    
    Results are paginated. Use page and limit parameters to navigate. Default is 20 results per page, maximum 100.
    
    History is retained for 90 days. Account-level stats (total credits, balance) never expire.`,
          inputSchema: {
            page: z.number().int().min(1).optional().describe("Page number (default 1)"),
            limit: z
              .number()
              .int()
              .min(1)
              .max(100)
              .optional()
              .describe("Results per page, max 100 (default 20)"),
          },
        },
        async ({ page, limit }) => {
          if (!api.hasApiKey) return authError();
    
          try {
            const result = await api.history(page, limit);
            return successResult(result);
          } catch (err) {
            if (err instanceof ApiRequestError) return apiErrorToResult(err);
            return errorResult(err instanceof Error ? err.message : "Unknown error");
          }
        }
      );
  • src/index.ts:39-41 (registration)
    Top-level invocation of registerHistoryTool(server, api) to wire up the tool in the MCP server.
    registerHistoryTool(server, api);
    registerStatsTool(server, api);
    registerAllowlistTools(server, api); // list_allowlist, add_to_allowlist, remove_from_allowlist
  • The api.history() method that makes the actual HTTP GET request to /v1/history with optional page and limit query params.
    async history(page?: number, limit?: number): Promise<HistoryResponse> {
      const params = new URLSearchParams();
      if (page) params.set("page", String(page));
      if (limit) params.set("limit", String(limit));
      const qs = params.toString();
      return this.doRequest<HistoryResponse>(
        "GET",
        `/v1/history${qs ? "?" + qs : ""}`
      );
    }
Behavior4/5

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

No annotations provided, so description carries full behavioral burden. It discloses pagination behavior, data retention (90 days), and distinguishes between history and account-level stats. Missing details on sorting order or rate limits, but sufficient for a read-only history tool.

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?

Three concise paragraphs: first states purpose, second covers pagination, third covers retention. No fluff, every sentence adds value. Front-loaded with the core purpose.

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?

No output schema, but description explains return fields (URLs, scores, phishing status, credit usage). Also covers pagination and retention. Missing details on filtering or sorting, but overall adequate for a list endpoint.

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?

Both parameters (page, limit) are fully described in the input schema with defaults and constraints. The description repeats schema info without adding new semantics. With 100% schema coverage, baseline of 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 'View recent URL check history' and lists specific fields (scores, phishing status, credit usage). It implicitly differentiates from sibling tools like check_url (single check) and get_stats (aggregate stats).

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

Usage Guidelines3/5

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

Mentions pagination and parameter usage but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. Context from sibling names helps but description lacks direct guidance.

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/123Ergo/unphurl-mcp'

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