Allow record retrieval tools to utilize `fields` API param to conserve context

[andrewmitchell-automations]

I'm finding that when an agent tries to query a table (list_records, get_record, etc.) which has lots of linked/lookup fields, context fills up quickly - especially if the records it retrieves have a ton of connected records. This is one of the benefits of AirTable API's fields query param, which allows the requester to specify in their request which fields they'd like to get back.

I'd like to be able to add instructions to my agent that before calling any tool which returns record data, it should first call describe_table and determine which fields it NEEDS, and then only retrieve those specific fields. That requires exposing the fields query param to the applicable record-retrieval tools.

Might try this one myself, but before I do, @domdomegg is there any reason this WOULDN'T work?

Thanks!

[domdomegg]

Yeah I think this could work. My guess is that really the more generic solution might be using https://www.anthropic.com/engineering/code-execution-with-mcp in your client harness.