# Business profile and recipes

> MCP tools to read and complete the business profile and to get automation recipes from it.

- kind: mcp-tool
- status: stable
- access: write
- last_verified: 2026-10-07
- url: https://tilopay.com/en/developers/agentes/mcp/perfil

## What it covers [#que-cubre]

The agent keeps a short business profile: what the business does, what it sells, where it sells,
what its charges look like and what it wants to improve. From that profile it builds the
automation recipes it proposes to you, and it knows which question is still pending (the
questionnaire is four questions at most).

The profile is saved field by field: whatever is not sent is preserved. Recipes change with the
modules the user has enabled: banking recipes only appear when the
[banking API](/en/developers/agentes/mcp/api-bancario) is enabled.

These tools do not call the Tilopay API: they work on the MCP server's own data.

## Tools [#herramientas]

### View business profile [#tilopay-get-business-profile]

- `tilopay_get_business_profile`
- Access: Read only

Returns the business profile: the data the Tilopay account already has (name, line of business, location, phone, billing email, currencies, logo) and what is still missing to ask, with the next pending question.

**Parameters**

No parameters.

**Returns**

`{ profile, next_question, total_questions, is_complete }`

profile = the saved business profile (or null if there is none); next_question = the next pending onboarding question; total_questions = how many questions the questionnaire has; is_complete = whether the profile is already complete.

### Save business profile [#tilopay-save-business-profile]

- `tilopay_save_business_profile`
- Access: Write

Saves or completes the business profile with what the merchant answered or confirmed. It can save one field at a time; fields not sent are kept, and what is saved here is no longer overwritten by Tilopay data.

**Parameters**

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `business_type` | string | — | What the business does |
| `main_products` | string | — | Main products or services |
| `sales_channels` | string | — | Sales channels: in-store, online, social media, WhatsApp |
| `ticket_pattern` | string | — | What the charges look like: amounts, frequency, currency |
| `goals` | string | — | What the merchant wants to improve |
| `notes` | string | — | Additional useful details |
| `opening_hours` | string | — | Opening hours |
| `tone` | string | — | Communication tone with customers |
| `short_description` | string | — | Short business description |
| `social_links` | string | — | Website and social networks |
| `refund_policy` | string | — | Returns or refunds policy |
| `business_name` | string | — | Correction of the business name |
| `industry` | string | — | Correction of the business industry |
| `phone` | string | — | Correction of the business phone |
| `address` | string | — | Correction of the address |
| `invoice_email` | string | — | Correction of the billing email |

**Returns**

`{ profile, next_question, is_complete }`

profile = the already updated profile (fields that are not sent are kept); next_question = the next pending question; is_complete = whether the profile became complete with this save.

### Recipes and automations [#tilopay-recommend-automations]

- `tilopay_recommend_automations`
- Access: Read only

Returns suggested recipes and automations for the merchant based on their business profile and the active MCP modules.

**Parameters**

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | — | How many recipes to return (5 by default) |

**Returns**

`{ profile_complete, next_question, recipes }`

recipes = suggested recipes and automations based on the business profile and active modules (includes banking ones only when the user has BaaS enabled); profile_complete and next_question indicate whether the profile still needs completing.