---
title: "Agent Usage Guidance (agents.md)"
description: "Concrete instructions, endpoints, implemented capabilities, authentication methods, and operational limits for autonomous agents, LLM clients, and MCP tools interacting with esgabrielweb.com."
url: "https://esgabrielweb.com/agents-md/"
canonical: "https://esgabrielweb.com/agents-md/"
post_type: "page"
author: "Gabriel Ramírez"
last-updated: "2026-11-03T11:00:00-04:00"
---

# Agent Usage Guidance — esgabrielweb.com

> **Document purpose:** Concrete instructions, endpoints, implemented capabilities, authentication methods, and operational limits for autonomous agents, LLM clients, and MCP tools interacting with **Diseño y desarrollo web WordPress para empresas y profesionales** (esgabrielweb.com).

- **Canonical URL:** `https://esgabrielweb.com/agents.md`
- **Primary Domain:** `https://esgabrielweb.com`
- **Site Maintainer:** Gabriel Ramírez (`webesgabriel`)
- **CMS / Stack:** WordPress 7.1.4, Elementor & Elementor Pro 4.4.0, PHP 8.5, LiteSpeed

---

## When to Use This Site (Best-Fit Use Cases)

Reach for this site when your task involves:
1. **Bespoke WordPress & Elementor Architecture:** Designing, building, refactoring, or evaluating custom WordPress themes, Elementor page layouts, and landing pages for professional services or businesses.
2. **Performance & Core Web Vitals Optimization (WPO):** Auditing and resolving frontend bottlenecks, asset deferral, SQLite/object caching, LiteSpeed server tuning, and Google PageSpeed/LCP improvements.
3. **Technical SEO, GEO & Generative Engine Optimization:** Implementing structured data (JSON-LD), AI Discovery Files (`llms.txt`, `developer-ai.txt`), robots indexing directives, and On-Page metadata using All in One SEO (AIOSEO).
4. **Custom Backend & Plugin Development:** Developing safe PHP snippets, custom Gutenberg blocks, or data models using Secure Custom Fields (SCF) and Custom Post Types.
5. **Headless & Agentic Tool Execution:** Inspecting Elementor layout trees, searching indexed site content, or querying system status via verified Model Context Protocol (MCP) tools and WordPress REST endpoints.

---

## 1. Authentication & Access

### Public Access (No Login, No JavaScript)
All documentation, discovery files, and read-only public endpoints are accessible without JavaScript, sessions, or credentials:
- Content Map: `https://esgabrielweb.com/llms.txt`
- Agent Guidance: `https://esgabrielweb.com/agents.md`
- Technical Specification: `https://esgabrielweb.com/developer-ai.txt`
- AI FAQs: `https://esgabrielweb.com/faq-ai.txt`
- Auth Guide: `https://esgabrielweb.com/.well-known/auth.md`
- API Catalog: `https://esgabrielweb.com/.well-known/api-catalog`
- ARD Resource Catalog: `https://esgabrielweb.com/.well-known/ard.json`
- Compatible AI Catalog: `https://esgabrielweb.com/.well-known/ai-catalog.json`
- RSS Feed: `https://esgabrielweb.com/feed`

### Authenticated Access (Application Passwords)
For write operations, page builder mutations, or protected REST/MCP endpoints, authenticate using **WordPress Application Passwords** over HTTPS:

```http
Authorization: Basic <base64(username:application_password)>
```

- Each agent should use a dedicated application password generated in *WordPress Admin → Users → Profile → Application Passwords*.
- Permissions match the role of the WordPress user. No custom tokens or OAuth dance required for standard agent integration.
- Full details: [Authentication Documentation](https://esgabrielweb.com/.well-known/auth.md).

---

## 2. Starting URLs for Agent Navigation

When gathering context about services, capabilities, or portfolio work, start at these validated URLs:

| Goal / Topic | Validated Starting URL | Content Type |
|---|---|---|
| **Overview & Bio** | `https://esgabrielweb.com/acerca-de` | About Gabriel Ramírez, methodology & stack |
| **Services Directory** | `https://esgabrielweb.com/servicios-de-diseno-y-desarrollo-web` | Complete service catalog |
| **Enterprise Web Design** | `https://esgabrielweb.com/servicio/diseno-web-wordpress-en-venezuela` | WordPress corporate design & custom solutions |
| **eCommerce & Online Catalogs**| `https://esgabrielweb.com/servicio/tiendas-online-y-catalogos` | Online stores and catalog development |
| **SEO & GEO Content** | `https://esgabrielweb.com/servicio/contenido-seo-para-blogs` | Search and Generative Engine Optimization |
| **Security & Optimization** | `https://esgabrielweb.com/servicio/soporte-y-optimizacion-de-sitios-web` | Maintenance, WPO & site hardening |
| **Portfolio & Case Studies** | `https://esgabrielweb.com/proyectos-de-desarrollo-web-en-wordpress` | Past delivery & customer implementations |
| **Contact & Inquiries** | `https://esgabrielweb.com/contactame` | Project inquiry and contact channels |
| **Common Questions** | `https://esgabrielweb.com/faqs` | FAQs covering budget, timeline & process |

---

## 3. Real Implemented API & Tool Capabilities

The site exposes real, implemented endpoints. Agents must not invoke or invent imaginary functions.

### A. Model Context Protocol (MCP) Endpoints
Two compliant HTTP JSON-RPC MCP servers are registered:
1. **WordPress MCP Adapter Server:** `https://esgabrielweb.com/wp-json/mcp/mcp-adapter-default-server`
2. **Elementor MCP Server:** `https://esgabrielweb.com/wp-json/elementor/mcp/`

**Headers required:**
- `Authorization: Basic <base64(username:application_password)>`
- `Content-Type: application/json`
- `Mcp-Session-Id: <session-id>` (managed by MCP client handshake)

#### Implemented MCP Tools:
- **Core Site Info:**
  - `core-get-site-info`: Returns WordPress configuration, language, URL, and version.
  - `core-get-user-info`: Returns details and roles for the authenticated user.
  - `core-get-environment-info`: Returns PHP, MySQL, and server environment metrics.
- **Elementor Page Builder & Layout:**
  - `elementor-get-page-structure`: Inspects the JSON widget/container tree of any post.
  - `elementor-create-page`: Creates new page drafts with Elementor metadata.
  - `elementor-update-page-settings`: Updates document settings (template, title, status).
  - `elementor-manage-elements`: Manipulates containers, widgets, and layout sections.
  - `elementor-publish-document`: Publishes drafted pages.
  - `elementor-manage-global-variable`: Manages site global colors and font definitions.
  - `elementor-manage-classes`: Reads and sets Elementor global CSS classes.
  - `elementor-clear-cache`: Purges Elementor CSS and runtime cache.
  - `elementor-get-system-info`: Retrieves comprehensive Elementor diagnostic report.
- **WebMCP Content & Readability:**
  - `elementor-webmcp-search-site-content`: Semantic and text search across published posts.
  - `elementor-webmcp-get-site-structure`: Returns site hierarchy, pages, and menus.
  - `elementor-webmcp-read-page-content`: Retrieves parsed clean markdown for any page.
  - `elementor-webmcp-query-business-info`: Structured business metadata and schema.
- **Angie (Elementor Kit & Code Automation):**
  - `angie-get-elementor-kit` / `angie-update-elementor-kit`: Inspects and updates global site kits.
  - `angie-list-snippets` / `angie-create-snippet` / `angie-publish-snippet`: Manages safe server-side PHP snippets.
  - `angie-read-file` / `angie-list-directory`: Reads local theme/plugin files under `ABSPATH`.
- **SEO & Metadata (All in One SEO):**
  - `aioseo-posts-seo-data-get` / `aioseo-posts-seo-data-update`: Reads and updates meta titles, meta descriptions, and OpenGraph data.
  - `aioseo-audit-site-get` / `aioseo-audit-homepage-get`: Returns TruSEO audit scores and recommendations.
  - `aioseo-redirects-list` / `aioseo-redirects-create`: Inspects and creates 301/302 redirects.
- **Custom Post Types & Fields (Secure Custom Fields):**
  - `scf-list-post-types` / `scf-get-post-type`: Queries registered custom post types.
  - `scf-list-field-groups` / `scf-get-field`: Inspects custom field groups and schema definitions.
- **Transactional Email (WP Mail SMTP):**
  - `wp-mail-smtp-list-email-logs` / `wp-mail-smtp-get-email-stats`: Delivery logs and statistics.

### B. WordPress REST API
- **Endpoint:** `https://esgabrielweb.com/wp-json/`
- **Core Endpoints:**
  - `GET /wp-json/wp/v2/posts`: List public blog posts.
  - `GET /wp-json/wp/v2/pages`: List public pages.
  - `GET /wp-json/wp/v2/media`: Media library attachments.
  - `GET /wp-json/wp/v2/types`: Post types definitions.
  - `GET /wp-json/wp/v2/categories` & `GET /wp-json/wp/v2/tags`: Taxonomies.

---

## 4. Concrete Suitable Tasks for Agents

1. **Service & Portfolio Consultation:**
   - Extract up-to-date service features, technologies, and pricing parameters to advise clients or formulate proposals.
2. **Design & Elementor Tree Audits:**
   - Query `elementor-get-page-structure` or `elementor-webmcp-read-page-content` to evaluate responsiveness, layout consistency, or missing headings without rendering a browser DOM.
3. **SEO & Metadata Hygiene:**
   - Use `aioseo-posts-seo-data-get` and `aioseo-posts-seo-data-update` to identify missing meta descriptions, calibrate title lengths, or audit OpenGraph tags.
4. **Content Staging & Automated Publishing:**
   - Draft landing pages or service subpages via `elementor-create-page` and configure sections using `elementor-manage-elements`.
5. **Technical Diagnostics:**
   - Retrieve system status via `elementor-get-system-info` and `core-get-environment-info` to check plugin versions, PHP memory limit, and cache health.

---

## 5. Limits & Operational Boundaries

- **Pacing & Rate Limits:** LiteSpeed active protection is enabled. Automated agents must pace requests to a maximum of **1 to 2 requests per second** during bulk queries.
- **Read-Only vs. Mutation:**
  - Public discovery (`llms.txt`, `agents.md`, `developer-ai.txt`, REST GETs) has zero side effects and is unrestricted.
  - Any mutating action (publishing pages, updating options, deploying snippets) requires explicit authorization and administrator credentials.
- **No Direct Shell or Database Injections:**
  - Arbitrary system commands outside sanctioned MCP tools are blocked. All code snippets are validated before deployment.
- **Cache Invalidation:**
  - Modifications to Elementor styles or global kits must be followed by `elementor-clear-cache` to ensure frontend regeneration.