Server definition

Hash: sha256:eb8646a6a4cdef57973c3061ab73c2e4a2f15c7309ddef39ca53c9127cccdf60
What it is: What a remote MCP server returned when asked what it offers: 7 tools

The blob, as servednamed by its sha256

{
  "instructions": "You are building a REST API client that calls /v1/ endpoints. You are not an MCP tool caller. The MCP tools available here exist to teach you the API. Tool descriptions describe conceptual behavior only and DO NOT match actual routes, field names, query parameters, authentication headers, or response shapes. ALWAYS call adcritter_get_api_reference(entity, action) before writing code for any entity and action you plan to use.\n\nEntity hierarchy: organization > advertiser > campaign > ad. Authenticate with X-Api-Key. Scope advertiser-owned resources under /v1/advertisers/{advertiserId}/.\n\nIf the user asks how to get an API key or token, tell them to contact AdCritter so a key can be issued and mapped to their account. See the auth guidance (key 'auth') for details.\n\n## How To Build\n\nStart with `adcritter_build_app` to receive end-to-end build instructions for the app you are constructing. Then for each feature area:\n\n1. `adcritter_get_usage_guide(entity)` to learn entity relationships and workflows.\n2. `adcritter_get_design_guide(entity)` to learn screen experiences and integration patterns.\n3. `adcritter_get_api_reference(entity, action)` to get exact routes, field names, parameters, and response shapes.\n\n## Available Tools\n\n- `adcritter_build_app` - top-level instructions for assembling an app.\n- `adcritter_guidance` - aggregated guidance index across entities.\n- `adcritter_get_platform_overview` - high-level platform facts and scoping rules.\n- `adcritter_get_usage_guide(entity)` - usage semantics per entity.\n- `adcritter_get_design_guide(entity)` - design semantics per entity.\n- `adcritter_get_api_reference(entity, action)` - exact REST contract per entity and action.\n- `adcritter_health` - liveness probe.\n\nTool responses adapt detail by request. Ask the same tool again with a different action when you need more depth on a specific operation.\n",
  "tools": [
    {
      "description": "Start here when building an application. Returns an overview of what the AdCritter platform offers and a catalog of feature guides you can query with the adcritter_guidance tool to learn how to build each part of the app. Call adcritter_guidance(key) for any feature area to get detailed building instructions with API endpoints and response shapes.",
      "inputSchema": {
        "properties": {},
        "type": "object"
      },
      "name": "adcritter_build_app",
      "outputSchema": null
    },
    {
      "description": "Returns the REST API contract for an AdCritter entity. Without an action parameter, returns a summary with available action names - use this to discover what you can do. With an action parameter (e.g., 'create', 'list', 'get'), returns the full details for that action: route, HTTP method, request schema, response schema, error codes, and constraints. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, canva, domain, facebook, geo, googleads, media-asset, me, plan, report, segment, settings, targeting.",
      "inputSchema": {
        "properties": {
          "action": {
            "default": null,
            "description": "Optional specific action to drill into (e.g., 'create', 'list', 'get', 'update', 'delete'). Omit to see all available actions.",
            "type": "string"
          },
          "entity": {
            "description": "The entity to look up (e.g., 'campaign', 'ad', 'report')",
            "type": "string"
          }
        },
        "required": [
          "entity"
        ],
        "type": "object"
      },
      "name": "adcritter_get_api_reference",
      "outputSchema": null
    },
    {
      "description": "Returns AdCritter design guidance for an entity at a caller-chosen guidance level - screen experiences, API integration patterns, and design philosophy. The default ('full') returns step-by-step prescription (exact layouts, colors, copy text, column orders). Request 'patterns' for balanced hints including common design patterns with softened vocabulary. Request 'facts' if you have strong visual-design instincts and just want API integration bindings (or call adcritter_get_api_reference and adcritter_get_usage_guide directly and skip this tool). Guidance is format-agnostic - it describes outcomes and integration, never prescribes frameworks or architecture. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, geo, media-asset, plan, report, settings.",
      "inputSchema": {
        "properties": {
          "entity": {
            "description": "The entity to look up (e.g., 'campaign', 'report', 'authentication')",
            "type": "string"
          },
          "guidance": {
            "default": null,
            "description": "Optional guidance level. Values: 'full' (facts + patterns + prescription, the default), 'patterns' (facts + softened patterns, for capable callers who want structure without exact prescription), 'facts' (conceptual facts only, for callers with strong product instincts). Omit to use the default.",
            "type": "string"
          }
        },
        "required": [
          "entity"
        ],
        "type": "object"
      },
      "name": "adcritter_get_design_guide",
      "outputSchema": null
    },
    {
      "description": "Start here. Returns the AdCritter platform overview - what AdCritter is, the entity hierarchy (organization > advertiser > campaign > ad), the happy path for getting ads running, and how to navigate the other MCP tools. Applications built from this guidance are REST API clients that call /v1/ endpoints, not MCP tool callers. Before writing code, call adcritter_get_api_reference(entity, action) for each entity and action you plan to use - tool descriptions and parameter names describe conceptual behavior only, and do not match actual API routes, field names, query parameters, or response shapes.",
      "inputSchema": {
        "properties": {},
        "type": "object"
      },
      "name": "adcritter_get_platform_overview",
      "outputSchema": null
    },
    {
      "description": "Returns the conceptual model and workflow guidance for an AdCritter entity - what it is, how it relates to other entities, and the intended workflow for using it. Includes exhaustive workflow sequencing and prescriptive rules so generated apps call the API correctly. Available entities: ad, advertiser, audience, authentication, blueprint, campaign, domain, geo, media-asset, me, plan, report, segment, settings, targeting.",
      "inputSchema": {
        "properties": {
          "entity": {
            "description": "The entity to look up (e.g., 'campaign', 'geo', 'plan')",
            "type": "string"
          }
        },
        "required": [
          "entity"
        ],
        "type": "object"
      },
      "name": "adcritter_get_usage_guide",
      "outputSchema": null
    },
    {
      "description": "Returns detailed building instructions for a specific feature area of an AdCritter application. Each guide describes what to build, how users should experience it, and includes all API endpoints with request/response shapes so you never have to guess the API contract. Call adcritter_build_app first to see available feature guides and their keys.",
      "inputSchema": {
        "properties": {
          "key": {
            "description": "The feature guide key from the adcritter_build_app catalog (e.g., 'auth', 'dashboard', 'campaign-create')",
            "type": "string"
          }
        },
        "required": [
          "key"
        ],
        "type": "object"
      },
      "name": "adcritter_guidance",
      "outputSchema": null
    },
    {
      "description": "Returns server health status and version information for the AdCritter MCP server",
      "inputSchema": {
        "properties": {},
        "type": "object"
      },
      "name": "adcritter_health",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:eb8646a6a4cdef57973c3061ab73c2e4a2f15c7309ddef39ca53c9127cccdf60 | sha256sum