AdCritter for Builders

AdCritter ads platform: docs, API reference, app scaffolding, and white-label integration.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
70%
Calidad de los nombres
77%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (1)

  • LOWTool 'adcritter_get_platform_overview' name length outside 3-30 rangeen adcritter_get_platform_overview

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~1,071Tokens (definiciones de herramientas)
~561 BTamaño de respuesta típico
Impacto moderado en la atención (0.84% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "mcp-dev": {
      "url": "https://mcp.adcritter.com/mcp/dev"
    }
  }
}

Puntos de conexión remotos

https://mcp.adcritter.com/mcp/devstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (7)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
⚪adcritter_guidance(key)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "key": {
      "description": "The feature guide key from the adcritter_build_app catalog (e.g., 'auth', 'dashboard', 'campaign-create')",
      "type": "string"
    }
  },
  "required": [
    "key"
  ]
}
🟢adcritter_build_app

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.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢adcritter_get_platform_overview

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.

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢adcritter_get_api_reference(entity, action)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "entity": {
      "description": "The entity to look up (e.g., 'campaign', 'ad', 'report')",
      "type": "string"
    },
    "action": {
      "description": "Optional specific action to drill into (e.g., 'create', 'list', 'get', 'update', 'delete'). Omit to see all available actions.",
      "type": "string",
      "default": null
    }
  },
  "required": [
    "entity"
  ]
}
🟢adcritter_get_usage_guide(entity)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "entity": {
      "description": "The entity to look up (e.g., 'campaign', 'geo', 'plan')",
      "type": "string"
    }
  },
  "required": [
    "entity"
  ]
}
⚪adcritter_health

Returns server health status and version information for the AdCritter MCP server

Esquema de entrada

{
  "type": "object",
  "properties": {}
}
🟢adcritter_get_design_guide(entity, guidance)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "entity": {
      "description": "The entity to look up (e.g., 'campaign', 'report', 'authentication')",
      "type": "string"
    },
    "guidance": {
      "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",
      "default": null
    }
  },
  "required": [
    "entity"
  ]
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada7 herramientas
verificadoversión no registrada7 herramientas