Problem/Motivation

The entity_blueprint_config sub-module provides config entity serialization and operations, but these are not exposed as AI agent tools. AI agents cannot read, create, or manage config entities (views, image styles, field configs, etc.) through the standard tool interface.

Proposed resolution

New sub-module entity_blueprint_config_ai that exposes config entity operations as AiFunctionCall plugins, following the same pattern as entity_blueprint_ai for content entities.

Tools provided

  • ReadConfig — serialize a config entity to JSON in summary or full mode. The AI uses this to inspect existing configuration (e.g. read an image style to see its effects, read a view to see its displays).
  • ReadConfigSchema — generate a descriptive schema for a config entity type. The AI uses this to learn what properties are available before creating or modifying config.
  • CreateConfig — create a config entity from a JSON blueprint. Validates structurally and semantically before saving.
  • ManagePluginCollection — add, update, remove, or reorder plugins within a config entity's plugin collection. Covers use cases like adding image effects to an image style, managing view display handlers, or configuring field formatters.

Dependencies

Requires both entity_blueprint_config (for config operations) and entity_blueprint_ai (for EntityBlueprintToolBase and the backend resolver).

API changes

New AI tool plugin IDs:

  • entity_blueprint:read_config
  • entity_blueprint:read_config_schema
  • entity_blueprint:create_config
  • entity_blueprint:manage_plugin_collection

Comments

tim bozeman created an issue. See original summary.

  • tim bozeman committed 8c015acb on 1.0.x
    task: #3591630 Add AI tools for config entities
    
    By: tim bozeman
    
tim bozeman’s picture

Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.