Handle input_schema attributes that are specific to Apify

[jirispilka]

Some attributes, like prefill and editor: requestListSources, are specific to Apify, and LLMs won’t know how to use them by default.

For a complete list of attributes, see:
https://github.com/apify/apify-shared-js/blob/master/packages/input_schema/src/schema.json

We need to transform, modify, and enhance the tools with examples and clear descriptions to explain what these properties are and how they should be used.

[MQ37]

from the two you mentioned - prefill and editor; we are exposing only the prefill to the LLM. I do not think exposing the editor would make sense to expose to the LLM since that is UI related. I think we can change the logic to expose only the default - we would use value from prefill if available and if not use the default.

[jirispilka]

prefill is specific to Apify and isn’t part of the standard JSON schema, so LLMs don’t know what it means. We need to explain or handle it differently.

When the editor is set to requestListSources, do we let the LLM know that the array items are of type arrayItemsRequestListSources?
See reference.

[MQ37]

prefill is specific to Apify and isn’t part of the standard JSON schema, so LLMs don’t know what it means. We need to explain or handle it differently.

When the editor is set to requestListSources, do we let the LLM know that the array items are of type arrayItemsRequestListSources?
See reference.

Currently we do build nested schema for proxy and request lists - https://github.com/apify/actors-mcp-server/blob/master/src%2Ftools%2Futils.ts#L51

[jirispilka]

Cool. The goal of this task is to go through the list and make sure we’re handling everything specific to Apify.